Skip to Content
Product Information
Author's profile photo Andy Wang
Andy Wang
November 30, 2019 4 minute read

Trouble shooting for SOAP API Sales Order/Customer Return – Create, Update, Cancel (B2B)_1

1,Background

New inbound SOAP API is provided to API Hub. This asynchronous inbound service enables you as the supplier using SAP S/4HANA Cloud to automatically Create, Update, Cancel Sales Order/Customer Return. It is based on the SOAP protocol with namespace http://sap.com/xi/EDI/Supplier.

2,Error Handling

The information is sent in the request as a payload. Messages transferred by this service can be monitored using SAP Application Interface Framework (AIF) Monitoring.

3, Trouble shooting

Here you can proceed the correction according to below messages and procedures.

Purpose

On the Message Dashboard, you can analyze the deployed log.

Procedure

1. Log on to FLP and navigate to Message Monitoring tab. Open the Message Dashboard.

2. Choose Sales&Distribution EDI integration – /SDEDI

3. Choose All Messages to check all relevant AIF messages.

4. Below error messages are usually displayed in message dashboard.

4, Message Handling

From <https://blogs.sap.com?p=606>

Sales area cannot be determined

Diagnosis:

The system could not determine a sale area as no record has been specified in view EDI_V_EDSDC

System Response:

The system stops processing the EDI message

Procedure:

Define configuration for Assign Cutomer/Supplier to Sales Organiziong Data for integration with buyers.

Define in the SSC UI step Assign Customer/Supplier to Sales Organization Data with Buyers under Sales > Integration with Buyers

Business partner for role &1 cannot be determined

Diagnosis:

The system could not determine a sale area as no record has been specified in view EDI_V_EDPAR

System Response:

The system stops processing the EDI message

Procedure:

Define conversion from external to internal partner number for integration with buyers.

Define mapping in the SSC UI step Convert External to Internal Partner Numbers with Buyers under Sales > Integration with Buyers

No valid &1 party can be determined

Diagnosis:

The system could not determine an internal party ID as the a sale area as no record has been specified in view EDI_V_EDPAR

System Response:

The system stops processing the EDI message

Procedure:

Define conversion from external to internal partner number for integration with buyers.

Define mapping in the SSC UI step Convert External to Internal Partner Numbers with Buyers under Sales > Integration with Buyers

&1 must be provided in the source data

Diagnosis:

Necessary fields have to be provided in pay-load file.

For example, the system uses purchasing order number and purchasing order creation date in sales order.

System Response:

The system stops processing the EDI message

Procedure:

Provide those mentioned fields in Payload file or EDI segment fields

Sales document type cannot be determined

Diagnosis:

Sales documents type is not identified

System Response:

The system stops processing the EDI message

Procedure:

Provide sales document type in Payload file or EDI segment fields

Party type &1 is not supported

Diagnosis:

Party type in payload is not pre-defined in both buyer and supplier system:

Sold-to-party

Bill-to-party

Ship-to-party

Payer

Supplier

System Response:

The system stops processing the EDI message

Procedure:

Provide supported party type in Payload file or EDI segment fields

The Source Party internal ID must be provided in the source data

Diagnosis:

Necessary field internal ID of sender party have to be provided in pay-load file

System Response:

The system stops processing the EDI message

Procedure:

Provide internal ID in Payload file or EDI segment fields

Pricing procedure cannot be determined

Diagnosis:

The system could not determine a pricing procedure as no record has been specified in view V_T683V with:

Sales organization

Distribution Channel

Division in payload file.

System Response:

The system stops processing the EDI message

Procedure:

Define Pricing Procedure Determination for Sales.

Define Determination in the SSC UI step Set Pricing Procedure Determination under Sales > Pricing

Price conditions for customer expected price cannot be determined

Diagnosis:

The system could not determine a pricing procedure as no record has been specified in view V_T683V with:

Sales organization

Distribution Channel

Division in payload file.

System Response:

The system stops processing the EDI message

Procedure:

Define Pricing Procedure Determination for Sales.

Define Determination in the SSC UI step Set Pricing Procedure Determination under Sales > Pricing

Standard ID of the sender partner is not defined uniquely

Diagnosis:

There are multiple Standard IDs defined in payload

System Response:

The system stops processing the EDI message

Procedure:

Redefine the standard ID in sender partner to ensure it is the unique

Purchase order &2 of customer &1 is referenced by multiple sales orders

Diagnosis:

There are multiple sales orders are determined by purchasing order number in payload file

System Response:

The system stops processing the EDI message

Procedure:

Delete or Reject the sales orders with the duplicated purchasing order number reference , via in Change Sales Order app.

Purchase order &2 of customer &1 is currently being processed

Diagnosis:

The system locked the sales order with referred purchasing order number right now

System Response:

The system stops processing the EDI message

Procedure:

Unlock the sales order and process again

Sales document items cannot contain Sold-To-Party information

Diagnosis:

The system check the sold-to-party information on item in payload file

System Response:

The system stops processing the EDI message

Procedure:

Remove the sold-to-party information on item payload file or segment fields

Schedule line requested delivery date must be provided in the source data

Diagnosis:

The error happens when the schedule line requested delivery date is initial on schedule line in payload file

System Response:

The system stops processing the EDI message

Procedure:

Provide schedule line requested delivery date in Payload file or EDI segment fields

The salutation text &1 is not supported

Diagnosis:

The error happens when form of address provided in payload file is check failed in business partner

System Response:

The system stops processing the EDI message

Procedure:

Maintain the address information in Business Partner app with information in payload

The text procedure cannot be determined

Diagnosis:

The system could not determine text procedure as no record has been specified with sales document type in view V_TVAK_TXT

System Response:

The system stops processing the EDI message

Procedure:

Maintain the correct text procedure information

The text ID for the received text type &1 cannot be determined

Diagnosis:

The system could not determine a text type as no record has been specified in view EDI_V_TXTIN_SUP

System Response:

The system stops processing the EDI message

Procedure:

Define mapping for inbound texts type for integration with buyers.

Define mapping in the SSC UI step Define Mapping for Inbound Texts for Integration with Buyers under Sales > Integration with Buyers

Assigned Tags

      2 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Sai Giridhar Kasturi
      Sai Giridhar Kasturi

      thanks for sharing Andy...

      Author's profile photo Christopher Linke
      Christopher Linke

      Hello Andy Wang ,

      thank you very much for these information. I'm having problem with creating a Sales Order with a Text Position (TATX). Those positions don't have a ProductID or Quantity, but I don't find a way to create those. Here's my payload:

      <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edi="http://sap.com/xi/EDI">
   <soapenv:Header/>
   <soapenv:Body>
      <edi:OrderRequest>
	<MessageHeader>
		<CreationDateTime>2022-03-17T12:00:00Z</CreationDateTime>
		<SenderParty>
			<InternalID>1000171</InternalID>
		</SenderParty>
	</MessageHeader>
	<Order>
		<PurchaseOrderID>CL_TEST</PurchaseOrderID>
		<PurchaseOrderCreationDate>2022-03-10</PurchaseOrderCreationDate>
		<SalesDocumentType>TA</SalesDocumentType>
		<SalesOrganization>1010</SalesOrganization>
		<DistributionChannel>10</DistributionChannel>
		<OrganizationDivision>00</OrganizationDivision>
		<TransactionCurrency>EUR</TransactionCurrency>
		<Party PartyType="Supplier"/>
		<Party PartyType="SoldTo">
			<SupplierPartyID>1000171</SupplierPartyID>
		</Party>
		<Party PartyType="ShipTo">
			<SupplierPartyID>W101010</SupplierPartyID>
			<Address>
				<AddressName>Test GmbH</AddressName>
				<AddressAdditionalName>Potsdam</AddressAdditionalName>
				<StreetAddressName>TEst 1</StreetAddressName>
				<PostalCode>14478</PostalCode>
				<CityName>Potsdam</CityName>
				<Country>DE</Country>
			</Address>
		</Party>
		<RequestedDeliveryDate>2022-03-21</RequestedDeliveryDate>
		<OrderItem>
			<PurchaseOrderItemID>10</PurchaseOrderItemID>
			<PurchaseOrderItemCategory>TATX</PurchaseOrderItemCategory>
			<SalesOrderItemCategory>TATX</SalesOrderItemCategory>
			<OrderItemText>Kundentext</OrderItemText>
		</OrderItem>
	</Order>
      </edi:OrderRequest>
   </soapenv:Body>
</soapenv:Envelope>

       

      That's the error I'm getting back:

       

      RequestedQuantity-Content must be provided in the must be provided in the source data
Product must be provided in the source data must be provided in the source data

      Any idea about how to fix this?

      Thank you,

      Christopher