SAP R/3 and SAP A1 - Trigger Configuration (Magic xpi 3.x)

You can use the SAP R/3 connector to trigger a flow. When used in this way, the SAP R/3 connector listens for IDoc type messages from the SAP R/3 server. When an IDoc message arrives, Magic xpi creates an XML file containing the IDoc information, and then triggers the flow.

The trigger definition process includes the selection of the IDocs that you want the SAP R/3 connector to monitor. To process the received IDoc, you should use the Mapper to choose a schema that is appropriate for the IDoc. A single trigger can be defined to handle multiple IDoc types.

Note: To receive IDocs, the SAP Java Connector needs the mapping between the SAP Gateway instance and its TCP port. The mapping is defined in your operating system's services file. Depending on your operating system, the services file can be found at: Windows: C:\WINDOWS\system32\drivers\etc\services Unix: /etc/services On machines where the SAP GUI is already installed, the complete SAP services list is updated by the SAP GUI installer. On other machines, it needs to be updated by manually adding the required mapping to the services file. The complete SAP services list can be found at the end of this topic.

The SAP R/3 Trigger Configuration dialog box contains the following fields:

Property	Description
Service Definition
Message Type	Enter the Message Type name, or click to get a list of Message Types from the SAP R/3 server. You can then select the required Message Type from the list.
IDoc Type	Enter the IDoc Type name, or click to get a list of IDoc Types from the SAP R/3 server. You can then select the required IDoc Type from the list.
Extension	If the IDoc contains extensions, you can click to access the IDoc Extensions list. You can select the required extension from the list, which contains the extensions received from the server.
ALE Update Status	Select Yes or No to define whether you want to update the status of the processed IDoc in the SAP R/3 server at the end of the flow.
Result Definitions
Store trigger IDoc in	Click to open the Variables List. Select the location where you want to store the IDoc that is generated by the trigger.
Store trigger information in	Select one of the following from the drop-down list to define the storage format for the information generated by the trigger: String (default) - the default return type is UserString The data will be received in the following structure: <Transaction ID> - <message type> - <Idoc type> - <extension>. XML - the default return type is UserXML Click to open the Variables List. Select the location where you want to store the information that is generated by the trigger.

Click OK to save the trigger definition. If the schema does not exist, Magic xpi retrieves the relevant information from the SAP R/3 server, and builds an appropriate schema.

Alternatively, you can click Cancel to exit without saving the changes.

In addition, you can:

• Click New to create a new line in the table.

• Click Delete to delete a selected line in the table.

• Click Refresh XSD to get the IDoc schemas for all of the selected IDoc types.

 

To use the SAP R/3 connector as a trigger:

1. From the Project menu, select Resources to open the Resource Repository. Here, you should define an SAP R/3 resource. This allows you to create the required connections to SAP databases. For more information on how to do this, click here. You cannot continue with the next step until you have done this.

2. From the Project menu, select Services to open the Service Repository. Here, you should define an SAP R/3 service. For more information on how to do this, click here. You cannot continue with the next step until you have done this.

3. Drag the SAP R/3 connector to Magic xpi's Trigger area. When you do this, the Component Properties dialog box opens.

4. Click the Component Properties dialog box's Settings tab. In the Service Name field, select one of the services that you previously defined in the Service Repository.

5. Click Configuration to open the SAP R/3 Trigger Configuration dialog box. Enter the relevant information.

6. When you have entered the relevant information in these parameters, click OK to save the information and to exit the SAP R/3 Trigger Configuration dialog box, or click Cancel to exit without saving.

7. Finally, click OK to save the information and to exit the Component Properties dialog box, or click Cancel to exit without saving.

8. Your SAP R/3 trigger should now appear in the flow pane's Trigger area.

Complete SAP Services List

Services Mappings

sapdp00  3200/tcp

sapdp01  3201/tcp

sapdp02  3202/tcp

sapdp03  3203/tcp

sapdp04  3204/tcp

sapdp05  3205/tcp

sapdp06  3206/tcp

sapdp07  3207/tcp

sapdp08  3208/tcp

sapdp09  3209/tcp

sapdp10  3210/tcp

sapdp11  3211/tcp

sapdp12  3212/tcp

sapdp13  3213/tcp

sapdp14  3214/tcp

sapdp15  3215/tcp

sapdp16  3216/tcp

sapdp17  3217/tcp

sapdp18  3218/tcp

sapdp19  3219/tcp

sapdp20  3220/tcp

sapdp21  3221/tcp

sapdp22  3222/tcp

sapdp23  3223/tcp

sapdp24  3224/tcp

sapdp25  3225/tcp

sapdp26  3226/tcp

sapdp27  3227/tcp

sapdp28  3228/tcp

sapdp29  3229/tcp

sapdp30  3230/tcp

sapdp31  3231/tcp

sapdp32  3232/tcp

sapdp33  3233/tcp

sapdp34  3234/tcp

sapdp35  3235/tcp

sapdp36  3236/tcp

sapdp37  3237/tcp

sapdp38  3238/tcp

sapdp39  3239/tcp

sapdp40  3240/tcp

sapdp41  3241/tcp

sapdp42  3242/tcp

sapdp43  3243/tcp

sapdp44  3244/tcp

sapdp45  3245/tcp

sapdp46  3246/tcp

sapdp47  3247/tcp

sapdp48  3248/tcp

sapdp49  3249/tcp

sapdp50  3250/tcp

sapdp51  3251/tcp

sapdp52  3252/tcp

sapdp53  3253/tcp

sapdp54  3254/tcp

sapdp55  3255/tcp

sapdp56  3256/tcp

sapdp57  3257/tcp

sapdp58  3258/tcp

sapdp59  3259/tcp

sapdp60  3260/tcp

sapdp61  3261/tcp

sapdp62  3262/tcp

sapdp63  3263/tcp

sapdp64  3264/tcp

sapdp65  3265/tcp

sapdp66  3266/tcp

sapdp67  3267/tcp

sapdp68  3268/tcp

sapdp69  3269/tcp

sapdp70  3270/tcp

sapdp71  3271/tcp

sapdp72  3272/tcp

sapdp73  3273/tcp

sapdp74  3274/tcp

sapdp75  3275/tcp

sapdp76  3276/tcp

sapdp77  3277/tcp

sapdp78  3278/tcp

sapdp79  3279/tcp

sapdp80  3280/tcp

sapdp81  3281/tcp

sapdp82  3282/tcp

sapdp83  3283/tcp

sapdp84  3284/tcp

sapdp85  3285/tcp

sapdp86  3286/tcp

sapdp87  3287/tcp

sapdp88  3288/tcp

sapdp89  3289/tcp

sapdp90  3290/tcp

sapdp91  3291/tcp

sapdp92  3292/tcp

sapdp93  3293/tcp

sapdp94  3294/tcp

sapdp95  3295/tcp

sapdp96  3296/tcp

sapdp97  3297/tcp

sapdp98  3298/tcp

sapdp99  3299/tcp

sapgw00  3300/tcp

sapgw01  3301/tcp

sapgw02  3302/tcp

sapgw03  3303/tcp

sapgw04  3304/tcp

sapgw05  3305/tcp

sapgw06  3306/tcp

sapgw07  3307/tcp

sapgw08  3308/tcp

sapgw09  3309/tcp

sapgw10  3310/tcp

sapgw11  3311/tcp

sapgw12  3312/tcp

sapgw13  3313/tcp

sapgw14  3314/tcp

sapgw15  3315/tcp

sapgw16  3316/tcp

sapgw17  3317/tcp

sapgw18  3318/tcp

sapgw19  3319/tcp

sapgw20  3320/tcp

sapgw21  3321/tcp

sapgw22  3322/tcp

sapgw23  3323/tcp

sapgw24  3324/tcp

sapgw25  3325/tcp

sapgw26  3326/tcp

sapgw27  3327/tcp

sapgw28  3328/tcp

sapgw29  3329/tcp

sapgw30  3330/tcp

sapgw31  3331/tcp

sapgw32  3332/tcp

sapgw33  3333/tcp

sapgw34  3334/tcp

sapgw35  3335/tcp

sapgw36  3336/tcp

sapgw37  3337/tcp

sapgw38  3338/tcp

sapgw39  3339/tcp

sapgw40  3340/tcp

sapgw41  3341/tcp

sapgw42  3342/tcp

sapgw43  3343/tcp

sapgw44  3344/tcp

sapgw45  3345/tcp

sapgw46  3346/tcp

sapgw47  3347/tcp

sapgw48  3348/tcp

sapgw49  3349/tcp

sapgw50  3350/tcp

sapgw51  3351/tcp

sapgw52  3352/tcp

sapgw53  3353/tcp

sapgw54  3354/tcp

sapgw55  3355/tcp

sapgw56  3356/tcp

sapgw57  3357/tcp

sapgw58  3358/tcp

sapgw59  3359/tcp

sapgw60  3360/tcp

sapgw61  3361/tcp

sapgw62  3362/tcp

sapgw63  3363/tcp

sapgw64  3364/tcp

sapgw65  3365/tcp

sapgw66  3366/tcp

sapgw67  3367/tcp

sapgw68  3368/tcp

sapgw69  3369/tcp

sapgw70  3370/tcp

sapgw71  3371/tcp

sapgw72  3372/tcp

sapgw73  3373/tcp

sapgw74  3374/tcp

sapgw75  3375/tcp

sapgw76  3376/tcp

sapgw77  3377/tcp

sapgw78  3378/tcp

sapgw79  3379/tcp

sapgw80  3380/tcp

sapgw81  3381/tcp

sapgw82  3382/tcp

sapgw83  3383/tcp

sapgw84  3384/tcp

sapgw85  3385/tcp

sapgw86  3386/tcp

sapgw87  3387/tcp

sapgw88  3388/tcp

sapgw89  3389/tcp

sapgw90  3390/tcp

sapgw91  3391/tcp

sapgw92  3392/tcp

sapgw93  3393/tcp

sapgw94  3394/tcp

sapgw95  3395/tcp

sapgw96  3396/tcp

sapgw97  3397/tcp

sapgw98  3398/tcp

sapgw99  3399/tcp