Error in Delivery using ME2O : "essential transfer parameters are missing"

When you do a delivery using ME20, you might get a error like this. Even though you check all the config, error might still exist. Check following, and specially the last point. That is what most people forget.

Good Luck!! Let's Config SAP!!!!

Don't forget to leave your ideas,comments and/or suggestions.

• OVX6 - Assign sales org/dist.ch/plant
• SPRO > MM > Purchasing > Purchase Order > Set Up Subcontract Order > Assign Delivery Type "LB" to Plant
• Create Customer Code(XD01) of Plant.
• Material Master has to be extended to the Sales Area
• SPRO > MM > Purchasing > Purchase Order > Set Up Stock Transport Order > Define Shipping Data for Plants > Assign the Customer Code  

Most importantly, check this. This is the setting most people forget to maintain.

Maintain the Shipping conditions in customer master.

BODS - Download data problem for foreign characters

Sometimes when you download data using BODS file tool, you don't see foreign characters in the file.
This happens due to missing setting in the file object.

Change the "Code Page" parameter in the File properties to "utf-8", and then download data again. Your problem will be solved.

Good Luck!! Let's Config SAP!!!!

Don't forget to leave your ideas,comments and/or suggestions.

BODS - Foreign characters not visible in tables

After retrieve data from external database, sometimes foreign characters are not correctly visible in BODS database. This is due to missing setting in table in BODS.
Change the following setting and then you will be able to see those characters.
Go to table properties and change the following attribute.

Good Luck!! Let's Config SAP!!!!

Don't forget to leave your ideas,comments and/or suggestions.

BODS - Table or View does not exist

When try to retrieve data from another database using Business Objects Data Services (BODS), sometimes ending with an error saying "Table or View does not exist.
This happens due to 2 reasons.

1. Table or view is not actually created in the source database.
2. Missing setting in BODS while running the job. If the first reason is not a problem, follow these steps and run the job again.

Good Luck!! Let's Config SAP!!!!

Don't forget to leave your ideas,comments and/or suggestions.

  BODS - Table or View Does Not Exist by sandunsulakshana

/AFS/SCHNITT value is not populating when using “/AFS/BAPI_MATERIAL_SAVEDATA”

When you try to update  /AFS/SCHNITT field using /AFS/BAPI_MATERIAL_SAVEDATA, that field is not getting updated. 

This is happening because of a missing customizing entry.

To update this field using this BAPI, you need to follow these steps.

• -> SAP Reference IMG 
• -> Logistics General 
• -> Material Master 
• -> Field Selection 
• -> Assign Fields to Field Selection Groups 
• -> New entries 

Field name : MARA-/AFS/SCHNITT
         Propose Field Content from the Reference : Check the same (X)
         Maintenance status : K

Save the entry - Press Back

In the field selection group for the field MARA-/AFS/SCHNITT
         Enter the value as 150.

Save the values.

Change SAP Standard Field description easily

In real time, you need several fields to maintain customer information. When there is no proper field is there in your transaction, you ended up with using a unused field. But what happens is the description is totally misleading or inappropriate with the ideal meaning of the real time usage.

Options for that sort of scenarios:

1. Create custom field in data dictionary and add it in the screen

2. Change the standard SAP description. If you use multiple languages, have to maintain in all

3. Live with it. Use the same SAP description and inform user to ignore the description

Here is the simplest and the recommended way to change description of a fields.

Good Luck!! Let's Config SAP!!!!

Don't forget to leave your ideas,comments and/or suggestions.

1.Go-to the relevant transaction. I use here Material master.

2. Locate the desired field

3. Press F1 and get the data element name.

4. Go-to SMOD transaction.

5. Follow this menu path

6. Enter the data element copied in the step 3.

7. You will get a screen to enter desired description.

The length of each field is :
- Short field label: 10 characters
- Medium field label: 20 characters
- Long field label: 40 characters
- Heading: 55 characters
- Short Description: 60 characters

8. Save it. You may need to add it to a transport request.

9. Now go back to the transaction. (MM03) Description has now changed.

10. Press F1, it displays the entered Short Description

Dynpro Does not exist short dump in RFQ (ME41) or other purchasing documents

When executing the RFQ (Request For Quotation – ME41) after enter all entries, you might get this kind of a short dump.

This is the solution for that...

Good Luck!! Let's Config SAP!!!!

Don't forget to leave your ideas,comments and/or suggestions.

This may arise in other purchasing documents also. Problem is Enhancement MM06E005 is active in your system. But screens are not created or incorrect.

What you have to do is:

Option 1 : Go-to SMOD. Inactive ehancement MM06E005.

Option 2 : Go-to SMOD, Create and activate relevant sub-screen :

- SAPLXM06 -0101 – Sub-screen header purchase order
- SAPLXM06 -0201 – Sub-screen header outline agreement
- SAPLXM06 -0301 – Sub-screen header RFQ
- SAPLXM06 -0111 – Sub-screen item purchase order
- SAPLXM06 -0211 – Sub-screen item outline agreement
- SAPLXM06 -0311 – Sub-screen item RFQ

NOTE : You must identify all dynpros as sub-screens. It is not necessary that they contain fields. However, they must be available so that no program termination will occur.

Please also refer to SAP note 1517584, 389059 for relevant information.