Table of Content

1. Introduction 6
1.1 Document Purpose 6
2. Good Movement Idoc Errors (IDoc message type : WPUWBW) 6
2.1 Error : Purchase order not found for article &1 (Customizing Setting &2) 7
2.1.1 Root Cause 7
2.1.2 Fix Procedure 8
2.1.2.1 Article Not Listed in the Site 8

2.1.2.2 Net price not maintained for the Article-Site 13

2.1.2.3 Article Blocked For Procurement in the Site 14

2.1.2.4 Purchase Order Document has been archived 15

2.2 Error : GR for PO &: remaining quantity not sufficient 16

2.2.1 Root Cause 16
2.2.2 Fix Procedure 16
2.3 Error : Cons.: Goods issue for PO item &1 &2 not posted yet OR No Delivery exists for the tracking
number &1 18
2.3.1 Root Cause 18
2.3.2 Fix Procedure 18
2.3.2.1 Goods Issue Not complete due to incomplete ULD (Unified Logistics Data) Data 18

2.3.2.2 Goods Issue Not complete due to Planned PGI Date of the delivery is in the past period 19

2.3.2.3 Goods Issue Not complete since the Pick and despatch process is not completed for the
delivery 20

2.3.2.4 Goods Issue or the Goods Receipt is not done due to master data issues 20

2.3.2.5 Goods Issue is not done since the delivery contains VERB article 20

2.4 Error : Quantity & “Delivery Completed” 21

2.4.1 Root Cause 21
2.4.2 Fix Procedure 21
2.5 Error : DREC Idoc & 3 & 1 doesn’t exist for GR & 2 & 4 24
2.5.1 Root Cause 24
2.5.2 Fix Procedure 24
 2.5.2.1 No Purchase requisition(PR) number found for the idocs 25

2.5.2.2 Idocs with Purchase Requisition(PR) number 25

2.6 Error : & exceeded by & & & 26

2.6.1 Root Cause 26
2.6.2 Fix Procedure 26
2.7 Error : Article & not maintained in site & 30
2.7.1 Root Cause 30
2.7.2 Fix Procedure 30
2.8 Error : The article & does not exist or is not activated 35
2.8.1 Root Cause 35
2.8.2 Fix Procedure 35
2.9 Error : No goods receipt possible for purchase order & & 38
2.9.1 Root Cause 38
2.9.2 Fix Procedure 38
2.10 Error: Goods receipt for purchase order &: qty not sufficient for cancellation 40
2.10.1 Root Cause 40
2.10.2 Fix Procedure 40
2.11 Error : Article & unkown in system 42
2.11.1 Root Cause 42
2.8.2 Fix Procedure 42
2.12 Error : WREC idoc: Some items cannot be matched for GR of &1 45
2.12.1 Root Cause 45
2.12.2 Fix Procedure 45
2.13 Error : Delivery completed indicator cannot be set for item & 49
2.13.1 Root Cause 49
2.13.2 Fix Procedure 49
2.14 Error : Base unit of measure & or article & unknown 53
2.14.1 Root Cause 53
 2.14.2 Fix Procedure 53
2.15 Error : EDI: Partner profile inbound not available 56
2.15.1 Root Cause 56
 2.15.2 Fix Procedure 56
2.16 Error : ISO unit of measurement not maintained for article & 60
2.16.1 Root Cause 60
2.16.2 Fix Procedure 60
2.17 Error : Enter a vendor for special stock & 63
2.17.1 Root Cause 63
2.17.2 Fix Procedure 63
1. Introduction

IDocs are an integral part of SAP R/3 ERP solution due to its extensive use in SAP for data
communication. Most of the TCS clients across various business domains those who have implemented
SAP ERP solution are investing considerable amount of effort in monitoring the IDocs since IDocs
maintenance plays a key role in SAP application stabilization from business data accuracy perspective.

The term IDoc stands for “Intermediate Document”. IDoc is an standard SAP object that carries data of
a business transaction from one application system to another in the form of electronic message.
The transfer from SAP to non-SAP system is done via EDI (Electronic Data Interchange) subsystems
whereas for transfer between two SAP systems, ALE is used.

EDI (XML
(Electronic Data
SAP IDoc Non SAP
Conversion) Exchange)

(Application Link
SAP IDoc SAP
Enabling)

1.1 Document Purpose

This Document describes some of the common errors in Goods Movement IDoc processing and the
resolution approach to address the failed Idocs.
2. Good Movement Idoc Errors (IDoc message type : WPUWBW)

IDocs with message type WPUWBW is used to transfer goods movement data from POS (point of sales)
to SAP retail system.

Below are the information transferred via this IDoc type.

Control Record
- IDoc creation Date and Time
- Message Type
- Staus
- Partner( Sender/Receiver)

Data Record
- Purchase Order/Delivery
- Article
- Quantity
- Movement Type
- Other Goods movement data

Find below some of the frequently used movement type for the IDocs with message type WPUWBW

MOVEMENT TYPE DESCRIPTION

101 Goods receipt for purchase order
102 Goods receipt for purchase order – Reversal/Cancellation
122 Return delivery to supplier
161 GR Returns
201 Consumption for cost center
309 Article to Article movement
321 Transfer posting quality inspection to unrestricted
641 Goods Issue, stock in transit
Znn Customised Goods Movement Types

2.1 Error : Purchase order not found for article &1 (Customizing Setting
&2)

2.1.1 Root Cause

Goods movement WPUWBW IDocs fails with this error while processing the receipts if the line items
present in the receipt Idoc is not present in the purchase order due to the below possible reasons

● Article Not Listed in Site

● Net Price Not Maintained for the Article-Site
● Article Blocked for procurement in the Site
● PO Document is already archived

2.1.2 Fix Procedure

2.1.2.1 Article Not Listed in the Site

➢ Execute Tcode SE16N and fetch all the erroneous Items-Store combos of the failed Idocs from
the table WPLST

➢ Collect the failed articles and sites combinations as highlighted below

➢ Execute Tcode WSL11 and enter the article and site as input and check if listing exists for the
articles and site combinations

➢ If No listing found for the Article-Site combinations then consult business to maintain the listing
and reprocess the IDocs. If listing of the Article-Site is irrelevant/not-required then move the
IDoc to 68 Status (No further processing)

➢ If listing already exists for the Article-Site combinations while verified in Tcode
WSL11(screenshot below shows listing exists) then add the failed line items(Articles) in the
Purchase Order and Re-process the IDocs. Steps to be followed to add the articles are
demonstrated below.
 ➢ Follow the below steps to add the articles in the PO

- Execute Tcode ME23N and enter the PO number to be edited by clicking “Other Purchase Order”
icon as shown below (Note: You can collect the PO of the corresponding Idoc either from the
Idoc (REFERENZNR field in E1WPG02 segment) or from the LSMW output)

- Go to edit mode in the PO screen and add the line items for which listing is there(only enter
Article number, quantity, UOM and Site and hit enter). Get these details from idoc as shown
below.
Idoc Screen(WE05)

PO Screen(ME23N)

- One by one add all the lines for which listing exists and once you are done with adding all the
lines go to messages and select all the yellow message and delete those. This is to avoid
interfaces to downstream systems.

- Perform a check and if there are no errors then save the PO. If any errors found in any line item
the DO NOT add that line item in the PO.

2.1.2.2 Net price not maintained for the Article-Site

 ➢ Execute Tcode SE16N and fetch all the erroneous Items-Store combos of the failed Idocs from
the table WPLST

➢ Collect the failed articles and sites combinations as highlighted below

➢ Try to add the failed articles in the PO, which are not present in the PO. While adding the articles
system will display the below message if the Price for the article is not maintained. Consult
business to maintain the price for the article, once price is maintained add the missing/failed
articles in the Purchase Order and re-process the IDocs.

2.1.2.3 Article Blocked For Procurement in the Site

➢ Collect the failed article from WPLST table and check if the articles are Blocked for Procurement
by referring the PS Article status in Tcode MM43 (Logistics-Store View). The IDocs can be
moved to 68 status since the concerned Article has been blocked for procurement.

2.1.2.4 Purchase Order Document has been archived

➢ If the Purchase Order associated with the failed IDoc is already archived (neither showing in
ME23N Tcode nor present in EKKO table) then the failed Idoc can be moved to 68 status(no
further processing).
 2.2 Error : GR for PO &: remaining quantity not sufficient

2.2.1 Root Cause

Goods movement WPUWBW IDocs fails with this error while processing the receipts idocs to the below
possible reason

● Receipt quantity in the failed IDoc is more than the Order quantity and if the PO is not marked
for over receipt

2.2.2 Fix Procedure

➢ Collect the failed articles and Po line item number from the table WPLST (as highlighted below)

➢ Tick mark the “Unlimited” flag in the corresponding PO line item which has failed. This can be
done either through Tcode ME22N or through Tcode MASS (Below screenshot is for ME22N)

➢ Optional Step : If you do not want the PO change interface to be flown down to down stream
systems or to the supplier then you can delete the outbound messages from ME22N screen. Most
of the times the outbound message to vendor is deleted in order avoid any duplicate order
confusion for the vendor. This step to be done before saving the changes done to the PO.
 ➢ Reprocess the IDocs through Tcode BD87 once the “Unlimited” flag is ticked in the PO line.

2.3 Error : Cons.: Goods issue for PO item &1 &2 not posted yet OR No
Delivery exists for the tracking number &1

2.3.1 Root Cause

Sometimes we see these errors if Goods Movement IDocs fails during SGR(Store Goods Receipt) process
due to below possible reasons therefore we need to clear the IDocs manually by following the standard
business process.

● Goods issue process is not complete due to various reasons (For example: ULD data not
maintained in the delivery, Planned PGI date in the delivery is not in current period, presence of
VERP article in the delivery)
● Goods are not yet picked in DC
● Good Receipt process is not complete

2.3.2 Fix Procedure

Fix Procedure depends on the root cause as mentioned above in section 2.3.1.

2.3.2.1 Goods Issue Not complete due to incomplete ULD (Unified Logistics Data) Data

➢ Maintain the ULD data in the Purchase Order header details(Tcode ME22N) and then perform
post goods issue process. Once PGI is done GR IDocs can be processed sucessfully.

2.3.2.2 Goods Issue Not complete due to Planned PGI Date of the delivery is in the past period
 ➢ Change the planned post goods issue date to the current period (Tcode VL03N) and then perform
post goods issue. Once PGI is done GR IDocs can be processed sucessfully.

2.3.2.3 Goods Issue Not complete since the Pick and despatch process is not completed for the delivery

➢ Advise DC to perform Pick and desptach for the delivery so that Goods issue process can be
completed in SAP. Once Goods issue is done GR IDocs can be processed sucessfully.

2.3.2.4 Goods Issue or the Goods Receipt is not done due to master data issues

➢ If the goods issue or goods receipt process is not complete due to some master data issues (For
example: Storage location not maintained in delivery lines, Unit of measure is incorrect, Item
category incorrect etc) then seek assistance from business users to maintain the appropriate data
and then perform the goods issue/goods receipt process.

2.3.2.5 Goods Issue is not done since the delivery contains VERB article

➢ Goods Issue wouldn’t have completed if there is a VERB article(Packaging material) therefore
we need to perform Goods Issue for this VERB article separately(if required) in Tcode MIGO.
However we need to make the quantity as ZERO in the delivery for the VERB article else PGI
cannot be done for the delivery. (Hint: Under environment tab under article master data you can
verify the article type as VERB).

Once Goods issue is done GR IDocs can be processed sucessfully.

2.4 Error : Quantity & “Delivery Completed”

2.4.1 Root Cause

Sometimes we see these errors if Goods Movement IDocs fails during SGR(Store Goods Receipt) process
due to below possible reasons therefore we need to clear the IDocs manually by following the standard
business process.

● Goods movement quantity is ZERO for ant of the articles present in IDoc (i.e. MENGE = 0)
● Rounded value of the goods movement quantity for any of the article is ZERO (For example if
quantity is 0.26 then it will be rounded to 0)

2.4.2 Fix Procedure

 ➢ Identify the failed articles either from WPLST or from the Tcode WPER. (Failed articles
highlighted in the below screenshot)

➢ Ensure the article document for the other artices in the failed Idoc (i.e the articles for which goods
movemnet quantity is not ZERO) has been posted.

Idoc shown in the below screen shot has 2 Articles out of which one has MENGE value of 13 EA
and the other has MENGE value of 0.00. The Idoc has failed due to the presence of article with
MENGE value 0.00. Before proceeding with aby action on this failed Idoc we need ensure if the
article with MENGE value 13 EA has been posted sucessfully.

➢ Once it is ensured that the articles with Non-Zero quantity value have been posted, the failed Idoc
can be moved to 68 status and then we need to follow-up with the source system (i.e store POS)
and advise them to restrict zero quantity value in the goods receipt Idocs from the store.

2.5 Error : DREC Idoc & 3 & 1 doesn’t exist for GR & 2 & 4

2.5.1 Root Cause

Goods Movements idocs from stores fails with this error if conversion of purchase requisition(PR) to
purchase order(PO) fails in SAP due to the below possible reasons.

● No purchase requisition(PR) number created for the WGSREQ Idoc from stores
● Net price issues for line items in the PO
● No data error issue but the idoc failed due to some system issues (example lock issues)
● Articles attached to the PO are not listed in the site

2.5.2 Fix Procedure

➢ A customised LSMW can be developed to identify wheter Purchase requistion number craeted
from the tracking number prsence in Idoc which came from stores

Screenshot below shows the output of a customised LSMW which shows whether PR number
exists.

Fix Procedure depends on the root cause as mentioned above in section 2.5.1.

2.5.2.1 No Purchase requisition(PR) number found for the idocs

 ➢ Find the corresponding WGSREQ Idoc which came from stores and try to reprocess the
WGSREQ Idoc and see if it is creating the PR number properly. If it fails again then idnetify the
issue with the WGSREQ Idoc and fix accordingly. However the already failed WPUWBW Idoc
can be moved to status 68.

2.5.2.2 Idocs with Purchase Requisition(PR) number

➢ Execute Tcode ME59, enter only 1 PR number at a time as input in the field “Purchase
Requisition”. Refer the below screen to ensure other parameters.

Below are the possible outputs expected after executing the above step and respective fix procedures.

(i) Line item with Net Price issues

● The details of this idoc need to be emailed to business support so that the price can be maintained
● DO NOT close the idoc, re-process the ME59 step once the price is fixed so that PR to PO
conversion can be done.

(ii) No Errors

● Execute ME59 after removing the “Test Run” option so that PR will be converted to PO
● Re-process the failed IDoc through Tcode BD87 with idoc number as input

(iii) Article not listed error

● The details of this idoc and article-site need to be emailed to business support so that the article
can be listed in the concerned site
● DO NOT close the idoc, re-process the ME59 step once the price is fixed so that PR to PO
conversion can be done.

2.6 Error : & exceeded by & & &

2.6.1 Root Cause

Goods Receipt idocs from stores fails with this error for the below possible reasons.

● GR is already done at PO level instead of delivery (Note: A delivery from DC contains multiple
POs)
● GR probably already done manually by users therefore the GR Idocs has failed

● GR quantity in the IDoc is more that the Goods issues quantity in the delivery/PO

2.6.2 Fix Procedure

➢ Collect the external delivery number or PO or delivery from the failed idoc’s BONNUMBER
field in parent segment

➢ If external delivery number is present the BONNUMBER then fetch the corresponding delivery
number (VBLEN) from LIKP table by giving external delivery number(LIFEX) as input.
➢ Verify if the goods receipt is already done for the concerned deliveries or POs. We can verify the
receipt completion for delivery either from Tcode VL03N or from the Tcode MIGO. Similarly
through Tcode ME23N we can verify if the goods receipt is already done for the PO.
Below screenshot show that MIGO throws a messages which says “Goods receipt not possible
for delivery, error code 4” . This indicates the concerned delivery is already receipt and no
further goods receipt allowed.

➢ Sometimes we find GR is partially done for the delivery/PO and if we add the goods receipt
quantity came in the failed goods receipt idoc to the already receipted quantity then the summed
up quantity exceeds the goods issued quantity. In such case seek advise from business or the
DC/store to ensure physical goods receipt quantity at stores and then post the goods receipt
quantity in system accordingly.

2.7 Error : Article & not maintained in site &

2.7.1 Root Cause

Goods Receipt idocs from stores fails with this error for the below possible reasons.

● Failed article is not maintained in the concerned site

● Failed article is a generic article therefore cannot be maintained in a site
2.7.2 Fix Procedure

➢ Collect the article and site for which the IDoc has failed, this can be collected either from table
WPLST or from Tcode WPER.

➢ Maintain the Article in the site through Tcode MM42. Enter article-site in MM42 as input and
select “Logistics: store” view.

➢ Hit Enter until the below screen appears, save data when the below screen appears. Article
changed message will appears once it exits MM42 “Logistics: site” view. This indicates article is
now maintained in the site.
➢ Reprocessed the IDoc through Tcode BD87 if article is maintained in the site.

➢ Sometimes due to the nature of the article (for example : Generic article, article not presence in
system) we cannot maintain the article in the site through Tcode MM42. In such case the failed
IDoc can be moved to 68 status.

2.8 Error : The article & does not exist or is not activated

2.8.1 Root Cause

Goods Receipt idocs from stores fails with this error for the below possible reasons.

● Failed article is not available in the system

● GTIN came from stores in the goods movement IDoc Instead of article and the GTIN or
corresponding article not available in the system

2.8.2 Fix Procedure

➢ Collect the article for which the IDoc has failed, this can be collected from Tcode WPER.

➢ The article will throw the below error while displayed in “Display Article” scree. Tcode MM43.
 ➢ Seek advice from business to know why the article is not present in the system and proceed
accordingly. Possible reasons for the article not in the SAP system could be 1. Article/GTIN is a
new article and even before maintaining the article in SAP stores have received it 2. Article/GTIN
number came from site is incorrect 3. When the article was deleted from SAP the delete interface
to stores have not flown down. However if business maintain the article/GTIN in the system then
the failed IDoc can be re-processed otherwise the failed IDoc can be moved to 68 status after
confirming that the article document for the other good articles present in the IDoc have been
processed.

2.9 Error : No goods receipt possible for purchase order & &

2.9.1 Root Cause

Goods Receipt Idocs from stores fails with this error whenever the advanced shipment notice details from
vendor/DC are missing in the system before receipt posting. Goods receipt process expects advanced
shipment notice from vendor/DC so that receipts can be verified against the advanced shipment notice.

Note : Advance shipment notice(ASN) is an electronic message from vendor/DC which is being sent to
store prior to sending the physical goods and it contains the details of the goods which is to be delivered
from the Vendor/DC to the store.

However sometimes the advance shipment details are not available in the system in the PO due to below
possible reasons.

● Incorrect vendor profile setup in Vendor Master (System is expecting ASN from a vendor which
shouldn’t send)
● Store is receiving the goods without ASN for Purchase Orders which should be received against
ASN
● No ASN available in PO since either vendor/DC did not send it or the ASN has failed to process
in the system

2.9.2 Fix Procedure

➢ Collect the PO and line article for which the Goods receipt IDoc has failed, this can be collected
either from table WPLST or from Tcode WPER.

➢ Verify the “Confirmations” tab in the PO line to ensure if the ASN details are present.

➢ If the ASN details are present in the “Confirmation” tab then the IDoc can be processed otherwise
need to co-ordinate with the vendor/DC to resend the ASN so that goods receipt can be processed
after posting the ASN details. Before asking vendor/DC to resend the ASN we can check in SAP
if the vendor/DC has already sent the ASN but it has failed to process in the system.
 ➢ If it is found that due to incorrect Vendor Master set-up system is expecting ASN from a vendor
which shouldn’t send ASN then the failed goods receipt IDocs can be re-processed after changing
the confirmation tab in the PO to normal confirmations where no ASN is expected for
goods receipt posting. To fix the issue permanently for this particular scenario the
Vendor Master for vendor needs to be changed.

2.10 Error: Goods receipt for purchase order &: qty not sufficient for
cancellation

2.10.1 Root Cause

Goods Movement Idocs from stores fails with this error due to below possible reasons

● Goods Movement Idoc has movement type 102 (Reversal/cancellation) however the
cancellation/reversal quantity in the IDoc is more than the receipt quantity of the concerned PO
line.
● Reversal/cancellation request for a PO line which is not received at all.

2.10.2 Fix Procedure

➢ Collect the PO and line article for which the Goods receipt IDoc has failed, this can be collected
either from table WPLST or from Tcode WPER.

Check if the reversal/cancellation is possible. For example as per the screenshots below the IDoc has a
cancellation request of 5.00 CAR for the PO(line 30), however the receipt quantity in the PO line is only
1 CAR therefore the reversal/cancellation is not possible.

➢ If reversal is not possible then seek advice from business or the DC/store to ensure physical
goods cancellation quantity at stores and then post the goods cancellation quantity in system
accordingly.

2.11 Error : Article & unkown in system

2.11.1 Root Cause

Goods Receipt idocs from stores fails with this error for the below possible reasons.
 ● Failed article is not available in the system
● GTIN came from stores in the goods movement IDoc Instead of article and the GTIN or
corresponding article not available in the system

2.8.2 Fix Procedure

➢ Collect the article for which the IDoc has failed, this can be collected from Tcode WPER.

➢ The article will throw the below error while displayed in “Display Article” scree. Tcode MM43.
Seek advice from business to know why the article is not present in the system and proceed accordingly.
Possible reasons for the article not in the SAP system could be 1. Article is a new article and even before
maintaining the article in SAP stores have received it 2. Article number came from site is incorrect 3.
When the article was deleted from SAP the delete interface to stores have not flown down. However if
business maintain the article in the system then the failed IDoc can be re-processed otherwise the failed
IDoc can be moved to 68 status after confirming that the article document for the other good articles
present in the IDoc have been processed.

2.12 Error : WREC idoc: Some items cannot be matched for GR of &1

2.12.1 Root Cause

Goods Receipt idocs from DC fails with this error for the below possible reasons.

● Failed article is not available in the Purchase order against which it is being received
● Failed article is in deleted status in the Purchase order against which it is being received

2.12.2 Fix Procedure

➢ Collect the all the article and the PO from the failed IDoc. Below screenshot shows the failed
IDoc has 3 articles.
 ➢ Open the PO (REFERENZER) in ME23N and see if any of the articles present in the IDoc are
blocked in the Purchase Order. Below screenshot shows 2 articles which present in the IDoc are
in deleted/blocked status in the PO.
➢ Unblock/Undelete the concerned deleted article in the PO through Tcode ME22N and perform a
check after unblocking/undeleting just to ensure the PO doesn’t have any other issue. Seek advice
from business before unblocking the articles as business might have blocked the article for some
valid business reasons.

➢ Optional Step : If you do not want the PO change interface to be flown down to down stream
systems or to the supplier then you can delete the outbound messages from ME22N screen. Most
of the times the outbound message to vendor is deleted in order avoid any duplicate order
confusion for the vendor. This step to be done before saving the changes done to the PO.

➢ The Idoc can be re-processed through Tcode BD87 once the concerned lines are unblocked.

➢ If the articles present in th Idoc are not at all present in th PO then seek advice from business and
add the articles in the PO and then re-process the failed Idocs.

2.13 Error : Delivery completed indicator cannot be set for item &

2.13.1 Root Cause

Goods Receipt idocs from stores fails with this error for the below possible reasons.

● Delivery completed indicator was pre-set in the PO line due to which system doesn’t allow
receipt
● This scenario mostly occurs when there is a partial delivery

2.13.2 Fix Procedure

➢ Collect the article for which the IDoc has failed, this can be collected from Tcode WPER.
➢ Identify the delivery number from the IDOC

➢ If you verify the PO then mostly you will find two partial deliveries

➢ Even though the PO is due for Goods receipt the “Delivery Completed” flag is already set for the
PO

➢ From the below screenshots you can see the PO is closed even before the delivery is created

➢ To post the Goods Receipt and to re-process the failed Idoc remove the “Delivery Completed”
flag from the concerned PO line

➢ Re-process the Idoc through Tcode BD87 once the PO “Delivery Completed” flag is changed and
the changes to the PO is saved.
2.14 Error : Base unit of measure & or article & unknown

2.14.1 Root Cause

Goods Receipt idocs from stores fails with this error for the below possible reasons.

● Unit of measure of the article is incorrectly mentioned in the IDoc

2.14.2 Fix Procedure

➢ Identify the failed articles from the table WPLST or from Tcode WPER. Below screenshot shows
the Idoc failed due to article 440157

➢ From the below screenshots you can verify that in the IDoc the unit of measure for the article
440157 has been mentioned as CAR but in Article Display(Tcode MM43) the unit of measure for
the article is EA.

➢ Consult with business and the store to know the actual physical received unit of measure of the
concerned article and correct the unit of measure in master data or in the IDoc accordingly. IDoc
can be reprocessed once the unit of measure is corrected.

2.15 Error : EDI: Partner profile inbound not available

2.15.1 Root Cause

Inbound IDocs fails with this error for the below possible reasons.
 ● Partner profile not maintained for the partner number from which the IDoc has come
● Some parameters in the partner profile is incorrect

2.15.2 Fix Procedure

➢ Collect the IDoc message Type, message variant from the IDoc control record.

➢ Collect the partner number from the IDoc control record.

➢ Go to Tcode WE20 → Customer Record → Verify Concerned partner numbers inbound

parameters.
Note: Since the partner type is Customer(KU) we need to verify customer record in Tcode WE20.

➢ As we can see in the above screenshot that the IDoc has failed since the message type
“WPUWBW” and message variant “SGR” (these values present in failed IDoc) are not
configured in the Inbound parameters. Refer any other like store to know the details of the
Inbound parameter. Below screenshot shows that Inbound parameters for the site 2079 is being
referred to update the same parameters for site 2080.
 ➢ Maintain the Inbound parameters for Site 2080 as shown below.

➢ Re-process the IDoc through Tcode BD87. The IDoc will move to 64 status from status 56.

➢ Re-process the IDoc again through Tcode BD87. This time the IDoc will go to 53 status.

2.16 Error : ISO unit of measurement not maintained for article &

2.16.1 Root Cause

Inbound Goods movement IDocs from stores fails with this error for the below possible reasons.

● Unit of measure of the article is incorrectly mentioned in the IDoc

2.16.2 Fix Procedure

➢ From the failed IDoc Identify the article/line which has incorrect unit of measure. Screenshot
below shows in the IDoc segment E1WPG02 the unit of measure(MEINH) of the article has been
mentioned as KG whereas as per SAP standard it should be KGM.
 ➢ Change the Unit of measure(MEINH) value of the article in the IDoc by double clicking on the
E1WPG02 segment and then by following the steps shown in the below screenshots.

➢ Once the changes are done in the IDoc, save the IDoc and then re-process the IDoc through
Tcode BD87.

2.17 Error : Enter a vendor for special stock &

2.17.1 Root Cause

Inbound Goods movement IDocs from stores fails with this error for the below possible reasons.

● If source list is not maintained for an article for which purchase info record is maintained for
multiple vendors
● If there is unrestricted stock available for the article in the concerned site

2.17.2 Fix Procedure

➢ Identify the erroneous articles either from the Tcode WPER or from the table WPLST.
Screenshots shown below shows the IDoc has failed for 3 articles for site 3167.

➢ Check in EINA table if purchase info record is present for multiple vendors for the failed articles.
Below screenshot shows for the articles 352873, 353871 and 353869 there are purchase info
record present for two vendors.
➢ Check in EORD table if source list is maintained for the articles and site(3167), if there is no
record exists in EORD table then request business to maintain source list for the article and site
combination. The failed IDocs