Anda di halaman 1dari 2

3.

Importing the BAPI: Note: This entire documentation refers to IDES SAP system, refer the below scree n shot for detail. The following Process indicates how to import the BAPI.

4. Processing the BAPI: In this BAPI the mandatory importing and Tables parameters required to create a Contract are: 1. Sales Document Type (Importing Parameter) 2. Sales Organization (Importing Parameter) 3. Distribution Channel (Importing Parameter) 4. Division (Importing Parameter) 5. CONTRACT_PARTNERS (Tables Parameter) We can call this BAPI in a query transform and give the inputs as shown below. B efore calling the BAPI create a output schema for passing the Tables parameter a s shown below. Mapping Inside the Query from the above screen shot. Calling the BAPI inside the Query_1 as shown below. Select the required BAPI and pass the mandatory parameters as shown below. To pass the table s parameter, click the arrow as shown below and map the correct schema which is defied for partners. Double click on the query to map with the schema.

Pass the required return parameters to check the output. As the structure belongs to NRDM, need to unnest the structure as shown below. Finally execute the JOB to check the contract created. As shown above the Contract 40000227 has been created successfully. Check the sam e in the SAP system using the transaction VA43 .

5. Considerations in BAPI: Consider the following issues: All character values must be uppercase Padding values Assumed decimal values (QTY) Codes are language-specific Automatic type conversion SAP ERP or R/3 version-specific behavior To determine the data requirements of various SAP ERP or R/3 functions, you can read the function requirements in the SAP GUI transaction screens: BAPI list by functional area: bapi

BAPI and RFC source and input and output parameters: SE37 You can also determine appropriate values, such as the language-specific code va lues, by looking at the table where the data is ultimately stored. 6. Calling RFC s enabled Function Module: One solution would be to RFC-enable the function. That is a SAP provided functio n, I guess the better idea is to write a new function which does nothing else th an calling this function and enable RFC. For example to call the Function module READ_TEXT which was a normal function one, copy the same function module and make it RCF enabled. The following steps are required to enable the RFC. Create a new function module in the transaction SE37 ZREAD_TEXT and assign to func tion group ZTEST_GRP as shown.

Anda mungkin juga menyukai