Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_EDX_SP_LP_NAM | Define Logical Port Names |
Transaction Code | S_EBS_44000363 | (empty) |
Created on | 20110124 | |
Customizing Attributes | SIMG_EDX_SP_LP_NAM | Define Logical Port Names |
Customizing Activity | SIMG_EDX_SP_LP_NAM | Define Logical Port Names |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | EDX_SP_LP_NAM |
Use
In this Customizing activity, you define logical port names for a Web service interface.
Instead of using middleware (such as SAP PI), you can also provide DocumentSet messages direct from the SAP back-end system to the service provider. You can also retrieve new, pending DocumentSet messages at the service provider direct.
There is a Web service interface available for this in the Billing Consolidation Connector solution.
Requirements
- You do not wish to use middleware (SAP PI) as a message router.
- The DocumentSet messages sent by the service provider for this customer are signed. The IDOc and the PDF that are in the signed DocumentSet message are signed, and the signature is verified at the same time. Consequently, a VerifyLog is also found in this DocumentSet message.
- No verification of signed DocumentSet messages is possible in the SAP back-end system.
- Verification is undertaken by the service provider. This means signed and verified DocumentSet messages are sent by the service provider.
- You register the SSL certificates in the SAP back-end system that you use to communicate with the service provider.
- You have created a corresponding port in the SOA Manager.
Standard settings
Activities
You have to construct communication secured by certificate for secure dispatch of DocumentSet messages to the service provider. You have to register an SSL communication certificate in the SAP back-end system for this purpose.
To do this, you proceed as follows:
- Call transaction STRUST.
- Create a new SSL client identity under Environment -> SSL Client Identities:
- Make all of the necessary entries, and select key length 1024 or 2048.
- Create a certificate request, and send the file for signing to your Certification Authority (CA).
- Import the signed certificate response for the SSL client identity.
- Add your own CA using Certificate -> Database -> Execute to the list of trusted CAs.
If your own CA is not available in the list, include it.
- Link the newly created CA with the certificate.
To do this, in the trust manager via Certificate -> Import create the link for the certificate file (File tab) with the CA inserted in the database (Database tab).
In addition, you have to make the following entries in table EDX: Table: Service Provider, Logical Port (EDX_SP_LP_NAME):
- ID of Service Provider:
Enter the ID of the service provider here. Note that only numbers are allowed.
You can find an overview of the service provider IDs in the system in table EDX: Business Partner/Service Provider/Reporting Details(EDX_BP_SP).
- Name of Service Provider:
Enter a recognizable name for the service provider here.
- Name of Logical Port:
Name of the corresponding port that you have created in the SOA Manager.
Report EDX: Send Messages (EDX_SEND) is used to send the DocumentSet messages to the service provider. In table EDX: Configuration (General) (EDX_SETUP), select the middleware Web Service.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
EDX_SP_LP_NAME | S - Table (with text table) | SM30 |
History
Last changed by/on | SAP | 20110124 |
SAP Release Created in | 606 |