Inbound File Path Settings
Exercise 6: Runtime behaviour
Exercise Objectives
After completing this exercise, you will be able to:
• Exchange documents with business partners using the Outbound and Inbound Process.
Business Example
XYZ Ltd, a leading car manufacturer, has recently implemented the EDI Integration Technology for the sales and procurement transactions with its business partners. As a member of the EDI project team, you need to exchange documents with business partners using the Outbound and Inbound Process.
Task 1:
Check the runtime behavior:
1. Create a purchase order in the same way as in the exercise for message control.
2. Write down the IDoc number for your order.
3. Check the files in the directory <Path1> . Which file belongs to the IDoc created by you? The subsystem has not been started. If Do not start subsystem is set in the partner profile, at which level would you start the subsystem?
4. Change the partner profile for the partner T-BIL## and message type ORDERS to Start subsystem .
5. Re-enter the purchase order according to step 1 of this task. Check the status of the IDoc using the Status Monitor (BD87). Has the subsystem been started?
6. For this exercise, the subsystem is simulated by a program that receives the IDoc for a purchase order and generates a purchase order confirmation. The steps Convert IDoc to EDI document and send to vendor and Receive purchase order confirmation from vendor and convert to IDoc are then skipped. An IDoc file for the purchase order confirmation is saved in the directory <Path1> . The file name includes the IDoc number. You therefore need to delete the IDoc file you created in step 5 of this task from the directory <Path1> and find the file for the purchase order confirmation instead.
Continued on next page
Task 2:
Trigger inbound processing for the IDoc for the message type ORDRSP, using the program RSEINB00. Ensure the file you enter for the purchase order confirmation belongs to your purchase order.
1.
BIT320 Lesson: Inbound Process
Solution 6: Runtime behaviour
Task 1:
Check the runtime behavior:
1. Create a purchase order in the same way as in the exercise for message control.
a)
2. Write down the IDoc number for your order.
a)
3. Check the files in the directory <Path1> . Which file belongs to the IDoc created by you? The subsystem has not been started. If Do not start subsystem is set in the partner profile, at which level would you start the subsystem?
a) The subsystem would be started at the file or operating system level. If the subsystem does not start even when Start subsystem is set in the partner profile, the IDoc in the SAP system is set to status 20 and the process code EDIP is triggered. To restart IDoc processing with triggering the subsystem, use the standard task TS60001307.
4. Change the partner profile for the partner T-BIL## and message type ORDERS to Start subsystem .
a)
5. Re-enter the purchase order according to step 1 of this task. Check the status of the IDoc using the Status Monitor (BD87). Has the subsystem been started?
a) If the subsystem is started, the IDoc has status 18.
6. For this exercise, the subsystem is simulated by a program that receives the IDoc for a purchase order and generates a purchase order confirmation. The steps Convert IDoc to EDI document and send to vendor and Receive purchase order confirmation from vendor and convert to IDoc are then skipped. An IDoc file for the purchase order confirmation is saved in the directory <Path1> . The file name includes the IDoc number. You therefore need to delete the IDoc file you created in step 5 of this task from the directory <Path1> and find the file for the purchase order confirmation instead.
a)
Continued on next page
Task 2:
Trigger inbound processing for the IDoc for the message type ORDRSP, using the program RSEINB00. Ensure the file you enter for the purchase order confirmation belongs to your purchase order.
1.
a) In the selection screen, enter <Path1> <Filename>
BIT320 Lesson: Inbound Process
Lesson Summary
You should now be able to:
• Make appropriate settings for Inbound Processing
Unit Summary
You should now be able to:
• Describe the structure of an IDoc file
• Describe the method to make appropriate settings in the file port for Outbound Processing
• Describe the method to make appropriate subsystem settings
• Make appropriate settings for Inbound Processing
BIT320 Test Your Knowledge
Test Your Knowledge
1. The parameters specified in the documentation tools are the of the external record types and the
of the external segments.
Fill in the blanks to complete the sentence.
2. When specifying the file name during Outbound processing, the EDI_PATH_CREATE_CLIENT_DOCNUM function module generates names from the IDoc number.
Determine whether this statement is true or false.
□ True
□ False
3. At runtime, the program is started using the RFC connection.
Fill in the blanks to complete the sentence.
4. During Inbound Processing, which parameter defines the connection to an R/3 system in the STARTRFC program?
Choose the correct answer(s).
□ A -t
□ B -c
□ C -3
□ D -g
Answers
1. The parameters specified in the documentation tools are the version of the external record types and the release of the external segments.
Answer: version, release
2. When specifying the file name during Outbound processing, the EDI_PATH_CREATE_CLIENT_DOCNUM function module generates names from the IDoc number.
Answer: True
When specifying the file name during Outbound processing, the EDI_PATH_CREATE_CLIENT_DOCNUM function module generates names from the IDoc number. This guarantees that the names are unique. This function module is recommended by SAP.
3. At runtime, the program RFCEXEC is started using the RFC connection.
Answer: RFCEXEC
4. During Inbound Processing, which parameter defines the connection to an R/3 system in the STARTRFC program?
Answer: C
Inbound processing can be triggered from a Shell script (command file) using the program STARTRFC. You can specify the -3 parameter to define the connection to an R/3 system.