What is an IDoc?
IDoc or Intermediate Document is an SAP document format for business transaction data transfers.
This blog describes the detailed steps to be followed for setting up and sending an IDoc from an SAP R3 system to SAP BPM via SAP PI in a Process Orchestration setup.
An IDoc cannot be directly imported into SAP BPM. The WSDL generated from an imported IDoc in ESR is not WS-I compliant – hence you may face runtime issues when BPM tries to consume the service interface created of IDoc type.
Let us see how we can overcome this constraint and have the scenario run successfully.
Creation of Design objects
The IDoc we import from an SAP R/3 system will be used on the sender side but we cannot use this on the receiver side (BPM) because it is not WS-I compliant as mentioned in the earlier section. We need to modify certain tags before using it on the receiver side. (Note:1414292)
Note : To set a relevant type for a data object in BPM for an element, there needs to be a name associated with the complex type.
For example.. Below is the structure of the exported idoc in ESR
<xsd:element name="HRCC1UPTEVEN01"><xsd:complexType><xsd:sequence><xsd:element name="IDOC" type="HRCC1UPTEVEN.HRCC1UPTEVEN01"/></xsd:sequence></xsd:complexType>
We need to have an associated name to the complex type as shown below.
<xsd:element name="HRCC1UPTEVEN01" type=”named_example_complex_type”><xsd:complexType name=”named_example_complex_type”><xsd:sequence><xsd:element name="IDOC" type="HRCC1UPTEVEN.HRCC1UPTEVEN01"/></xsd:sequence></xsd:complexType>
Field | Sender Interface (SI_A) | Receiver Interface (SI_B) |
---|---|---|
Category | Abstract | Abstract |
Interface pattern | Stateless XI 3.0 Compatible | Stateless XI 3.0 Compatible |
Mode | Asynchronous | Asynchronous |
Request Type | Idoc | External Definition (3.d in Creation of wsdl section) |
2. Save and Activate all the changes.
Field | Sender | Receiver |
---|---|---|
Interface | SI_A | SI_B |
Adapter | Idoc_AAE | SOAP, XI 3.0, JPR URL |
Note : The WSDL might have errors as "s4s-att-invalid-value: Invalid attribute value for 'maxOccurs' in element 'element'.
Recorded reason: cvc-datatype-valid.1.2.1: '9999999999' is not a valid value for 'nonNegativeInteger'."
This can be ignored.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
18 | |
12 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |