Configuring the SAP system for ALE or BAPI inbound processing W...

http://pic.dhe.ibm.com/infocenter/radhelp/v9/topic/com.ibm.wsadapter...

IBM Rational Application Developer Version 9.0.1 > Developing > Developing enterprise applications > Connecting to enterprise information systems > Resource Adapters > WebSphere Adapters for PeopleSoft, SAP, Siebel, JD. Edwards, and Oracle > SAP Software > Configuring the module for deployment > Configuration on the SAP system

Configuring the SAP system for ALE or BAPI inbound processing

Before you configure WebSphere Adapter for SAP Software for ALE inbound processing or for BAPI inbound processing, you must configure authorization profiles and register an RFC destination on the SAP server. For ALE processing, you must also configure a receiver port, logical system, distribution model, and partner profile on the SAP server. Contact your system administrator if you are not sure whether these items have been configured. About this task Perform the following steps on the SAP server using the SAP GUI. Note: Only the first task is required for BAPI inbound processing. Procedure 1. Access levels required for the user name that is used to connect to the SAP system.: To run the SAP adapter smoothly, configure the following authorization profiles in the SAP system: Table 1. OBJECT B_ALE_RECV ALE/EDI: S_CTS_ADMI S_RFCACL S_TCODE S_RFC S_TABU_DIS S_IDOCCTRL S_IDOCDEFT

DESCRIPTION Receiving IDocs via RFC Administration Functions in the Change and Transport S Authorization Check for RFC User (for example, Trusted System) Authorization Check for Transaction Start Authorization check for RFC access Table Maintenance (via standard tools such as SM30) WFEDI: S_IDOCCTRL - General Access to IDoc Functions WFEDI: S_IDOCDEFT - Access to IDoc Development

AUTHORIZATION B_ALE_RC_ALL S_CTS_IMPALL S_RFCACL_ALL S_TCD_ALL S_RFC_ALL S_TABU_ALL S_IDCCTR_AL+ S_IDCDFT_ALL

To identify which authorizations are absolutely necessary, perform the following steps: a. Open TCode SM19 and use the Security Audit trace b. Run the SAP Adapter c. Refer to the system log SM20 for authorization objects that are either accessed or denied 2. Register an RFC program ID: a. Open transaction SM59 (Display and Maintain RFC Destinations). b. Click Create. c. Type a name for the RFC destination. d. In the Connection Type field, select T. e. In the Activation Type field, select Registered Server Program. f. Type a Program ID. You will use this program ID when you configure the adapter. This value indicates to the SAP gateway which RFC-enabled functions the program ID listens for.

1 of 3

14-Apr-14 16:43:PM

Configuring the SAP system for ALE or BAPI inbound processing W...

http://pic.dhe.ibm.com/infocenter/radhelp/v9/topic/com.ibm.wsadapter...

g. Under the MDMP and Unicode tab, set the RFC destination as Unicode or non-Unicode by choosing the appropriate radio button. For error-free operation of the adapter while using multiple language settings, set the RFC destination as Unicode. h. Save your entry. 3. Set up a receiver port (for ALE processing only): a. Open transaction WE21 (Ports in IDoc processing). b. Select Transactional RFC, click Ports, and click the Create icon. c. Type a name for the port and select OK. d. Type the name of the destination you created in the previous task (or select it from the list). e. Save your entry. 4. Specify a logical system (for ALE processing only): a. Open transaction BD54 (Change View Logical Systems). b. Click New Entries. c. Type a name for the logical system and click the Save icon. d. If you see the Prompts for Workbench request, click the New Request icon. Then enter a short description and click the Save icon. e. Click the Continue icon. 5. Configure a distribution model (for ALE processing only): a. Open transaction BD64 (Maintenance of Distribution Model). b. Click Distribution Model > Switch processing model. c. Click Create model view. d. Type a name for the model view and click the Continue icon. e. Select the distribution model you created, and click Add message type. f. For outbound processing, type the logical system name you created in the previous task as Sender and the logical name of the SAP server as Receiver. Then select a message type (for example, MATMAS) and click the Continue icon. g. Select the distribution model again and click Add message type. h. For inbound processing, type the logical name of the SAP server as Sender and the logical system name you created in the previous task as Receiver. Then select a message type (for example, MATMAS) and click the Continue icon. i. Save your entry. 6. Set up a partner profile (for ALE processing only): a. Open transaction WE20 (Partner Profiles). b. Click the Create icon. c. Type the name of the logical system you created in the earlier task and, for Partner Type, select LS. d. For Post Processing: permitted agent, type US and your user ID. e. Click the Save icon. f. In the Outbound parameters section, click the Create outbound parameter icon. g. In the Outbound parameters window, type a message type (for example, MATMAS05), select the receiver port you created in the earlier task, and select Transfer IDoc immed. h. Click the Save icon. i. Press F3 to return to the Partner Profiles view. j. In the Inbound parameters section, click the Create inbound parameter icon. k. In the Inbound parameters window, type a message type (for example, MATMAS), and a process code (for example, MATM).

2 of 3

14-Apr-14 16:43:PM

Configuring the SAP system for ALE or BAPI inbound processing W...

http://pic.dhe.ibm.com/infocenter/radhelp/v9/topic/com.ibm.wsadapter...

l. Click the Save icon. m. Press F3 to return to the Partner Profiles view. n. In the Inbound parameters section, click the Create inbound parameter icon. o. In the Inbound parameters window, type the following values: ALEAUD for Message Type, and AUD1 for Process Code. p. Click the Save icon. q. Press F3 to return to the Partner Profiles view. r. Click the Save icon. Results You have performed the tasks (on the SAP server) required to use the BAPI inbound interface or the ALE interface. What to do next Configure the adapter for the interface. Parent topic: Configuration on the SAP system

3 of 3

14-Apr-14 16:43:PM