No WPDNAC outgoing IDoc is generted

Hello community,
I have one IS RETAIL question
When new structured single article is created (that consists of empties BOM, one single component), outgoing IDOCs (towards POS) of type WPDNAC and WP_PLU are generated. Problem occurs when article is modified (for example when sales price changes) or article being re-listed: <b>NO WPDNAC IDoc IS GENERATED but only WP_PLU!
Could someone think of any reason why is it happening?</b>
I thought checking of WPDSET in customizing would do the trick, but it did not help.
I've already checked OSS notes, and didn't find any helpful notes (some problems from similiar notes were fixed in Relase 4.6, and we are running Release 4.7)

Hi,
I have similiar problem. When I create generic article with empties BOM and list it for the first time (via MM41 listing view or through WSM8,WSM4A,WSM4b,etc.), batch job that creates outbound idocs creates coresponding WP_PLU and WPDNAC idocs. Afterwards, whenever I list this same article to new site or change sales price for existing sites (VK11), only WP_PLU idoc is created, but no WPDNAC. This causes BOS on newly listed sites to miss connection between full article and emptie, and for the previously listed sites wrong price calculation.
Can anyone tell which changes cause creation of WPDNAC or in which cases it happens?
Today I fix this problem by manually sending complete generic article using WPMA transaction. This is obviously too late since "incomplete" generic article was previously sent to BOS and this only corrects the error after it caused trouble.

Similar Messages

How to Identify incoming and outgoing IDOC in the system for last one year.

Dear All,
How to Identify incoming and outgoing IDOC in the system for last one year.
Regards
Ashok

Dear Anindya,
I used WE05 the result by giving direction outbound.Then on created field i put the value date.I m getting the output in the no of idoc number.
This is only the way to identify?
Thnx
Ashok
Edited by: ashok singh on Oct 22, 2009 8:40 AM

How to identifi Incoming & outgoing IDOCS

Dear Basis Guru,
How to Identify the incoming and outgoing IDocs in the system for the last one year.
What is the use of IDOCS.
Kindly suggest for the same.
Regards,
Bipin.

Hi Bipin,
IDoc stands for intermediate document and its the structure used for data transfer between two SAP/non-SAP systems.
follow the link here for more information.
http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b815e43d711d1893e0000e8323c4f/frameset.htm
Regards,
Debasis.

Reg: Missing segment E1EDP01 in outgoing IDOC

hello guys,
I have got an issue in IDOC.
The idoc has a missing segment E1EDP01.
Flow is SAP to EAI to VENDOR.
I wnt to know why idoc is triggered without this segment E1EDP01.

How is this IDOC created? own programm?

User exit for outgoing IDOC

Hi friends,
I want to find user exit for outbound idoc INVOIC, but i dont to how to do that.
Please gve ur suggestions

INVOIC
Invoice / Billing document
- FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
- FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
- FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
- FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
- FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
- FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
- FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
- FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
- FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
- FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
- MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
- MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
- MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
- MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
- MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting

Populating the segments of idocs

Hi,
How do segments of the idoc get populated with data from SAP tables ? (for SAP standard idoc or newly created idoc and outbound process)
Can anyone say in details?
Good answer will be rewarded
Thanks ,
Manas Behera

For any IDOC there is a specific standard function module assigned that is called to fill the IDOC segments.
For orders it is e.g. IDOC_OUTPUT_ORDERS.
This function takes care of the filling of the IDOC segments. You also usually have user exits available in those function modules that you can use to manipulate the IDOC data or fill/add custom segments/fields.
The function modules usually start with IDOC_OUTPUT_* for outgoing IDOCS and IDOC_INPUT_* for incoming IDOCS.
Hope that helps,
Michael

Mapping Issue: one IDoc to multiple IDocs concerning incoming segments

Hi,
i want to devide one incoming IDoc to two or more outgoing IDoc's of same type concerning the appearance of one segment.
Incoming is:
   <IDOC BEGIN="">                   1...1
      <EDI_DC40 SEGMENT="">
      </EDI_DC40>
      <..>
      <Z1MOV SEGMENT=""> 0..99999
      </Z1MOV>
   </IDOC>
Target should be:
for each Z1MOV one IDOC.
   <IDOC BEGIN="">                   1...1
      <EDI_DC40 SEGMENT="">
      </EDI_DC40>
      <..>
      <Z1MOV SEGMENT=""> 0..1
      </Z1MOV>
   </IDOC>
I already did the occurance change, like imported target IDoc with changed attribute maxOccurs="unbounded".
I mapped the segment Z1MOV to IDOC but when Z1MOV occurs more than one time the target gets generated only one time. I changed the occurance of the IDoc to maxOccurs="unbounded".
What do i have to do to make it run?!
br

Can someone help?
When i switch to debug while testing message mapping i get following:
Close tag
Close tag
Start tag
Targetelement /ZIDOC/IDOC[2]/BEGIN kann nicht angelegt werden. Prüfen Sie, ob die XML-Instanz für die Ausgangs-XSD und die Zielfeldzuordnung die Anforderungen der Ziel-XSD erfüllt. Zielelement /ZIDOC/IDOC[2]/BEGIN kann nicht angelegt werden. Prüfen Sie, ob die XML-Instanz für die Ausgangs-XSD und die Zielfeldzuordnung die Anforderungen der Ziel-XSD erfüllt.
I hope you can get the idea of this error because i can't tanslate.
But the BEGIN is required for each message so how to get rid of it. This also concerns the SEGMENT-tag under each Segment of the IDoc.
br

Problem with HR inbound IDoc

Hi,
I have a problem with processing inbound IDocs from an external payroll system to infotype 0008. The process is quite simple; salary changes from the payroll system is recorded to the corresponding employee's infotype 0008. When testing I noticed that that the new record is recorded as is. For example if there is already an existing record with the validity dates 01.01.2010 - 31.12.9999 and the new record in the IDoc is 01.01.2011 - 31.12.9999, the new record is written as is. I would expect the system to delimit the old record correctly - similar to what would happen if you maintain records online. There is no error checking or any kind of processing done by the system.
I did some debugging and found out that the function module linked to process code HRMD writes the information directly to the database. If this is a standard way of doing this, it is really unusual.
Has anybody else encountered this? Any pointers?
Thanks.
Edited by: Theo Droste on Jan 20, 2011 11:56 AM

Hi
This is correct, the ale programme writes the data directly to the database, I have faced this isssue on occassion. I once raised an oss message on this as well, and sap confirms this is what happens. If it is a sap to sap ale, it somehow seems to work, - this could be because the outgoing idocs are created by sap itself but if it is a non sap to sap ale the onus is on us to ensure that the external system sends the correct data to sap in the way we intend it to be displayed.
that is how it has been in my experience. It is unusual, but apparently not impossible. Please let us know if you find out anything different.

How to see Segment Version in IDoc

Hi,
is there any way to see the Segment Version in an IDoc ?
We had the problem that an old version(Segment) was entered in the WE20(receiverdetermination) and we havent known this.
any ideas ?
Gordon

hi Michael,
that is not the thing i wanted.
If you have the newest version in WE31 but you have entered an old release in WE20 outbound parameters. The idoc is filled with the old segment version.
I only want to see the segment version in the outgoing idoc ?
IS there a way to see that ?
I have changed the release in we20 and after that the newest segment version was taken the idoc was ok!
Gordon.
Message was edited by: Gordon Breuer

OUTBOUND IDOCS PROCESSING ON ALE INTERFACE

Hi experts...
I am working on ALE IDOCS
I have a requirement where i have to convert my outgoing idocs into flat files on my local system
1) How do i create a file port and specify the location(directory)
2) How do i assign this file port to the sending system
3) Where will the idocs be stored ... can i check the location using AL11.
Can anyone send the procedure for the above ..
Also can anyone send me documents on "SAP to LEGACY system Interfacing"
to my mail id [email protected]
Thanks and Regards

Hi Ashok,
Please check this link.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2a1dd5d3-0801-0010-ed8d-bd797ed922cb
open it as PDF.
I think it will answer all your queries....
Dont forget to award points if you get the answer:-)
Regards,
Vinay

Missing IDoc - config question

I need to send SHPORD.DELVRY03 IDocs from SAP and convert it in XI to a file.
The outgoing IDoc in the SAP system has status
"03 - Data passed to port OK"
"The IDoc was sent to an R/3 System or an external program via a transactional RFC.
The TID is 0A62019724E14444EF7F0311."
Nothing however shows up in XI.
Any idea what to look into, what I need to check?
Don't know where to start, the connections were
set up between the source SAP system and the XI box.
Thanks a lot,
Viktor

Hi,
Is it may be because of Authorization Problem?
Just check this Thread.
I::000 what does it mean
Also check this-
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Hope this helps,
regards,
Moorthy

JDBC to Idoc mapping - create multiple Idocs from 1 JDBC input

I am importing data using JDBC and I want to put the data in an IDoc on a SAP system. my data is about 100,000 rows, but my Idoc (ZIDOC) is defined as 1-35,000 for the segments. I have followed Ossnote 814393, and also set up my Interface Mapping to use my JDBC source and the Idoc as the target. In my Message Mapping, i use the source as my JDBC Message Type, and the target is my External Definition Idoc (changed to be 1 to unbounded).
My incoming JDBC mapping is:
JDBCinput     (1:1)
-row            (0...Unbounded)
      -part        (1:1)
      -unit        (1:1)
      -type       (1:1)
my outgoing Idoc (from external definition) is:
ZIDOC           (1:1)
-IDOC          (1...Unbounded)
     -Begin       (required)
     -EDI_DC40 (1:1)
     -Zsegment   (1...35,000)
        -part        (1:1)
        -unit        (1:1)
        -type       (1:1)
I currently map JDBCinput = ZIDOC and IDOC, row = Zsegment, and the rest of the rows match.
When I use this mapping, my first 35,000 rows from my JDBC input gets mapped to ZIDOC with 35,000 segments, but the remaining 65,00 rows from my JDBC input just seem to be lost, as only this one ZIDOC is created. I would expect to see 3 Idocs created, 2 with 35,000 segments each, and the 3rd Idoc created with 30,000 segments.
Does anyone know what I need to change to get this mapping to work and create the extra needed Idocs? Can this be done with out using a BPM?
Any guidance?
Thanks
Jake

HI,
Just try out with context change and check if it works
In this type of case, it is easy to use Java mapping so that you can generate target structures as you like.
Hope this helps,
Regards,
moorthy

Document RFC Error in DEBMAS IDoc?

Hi Experts,
we use RFC to transfer DEBMAS-Idocs to a JCo-System.
Is it possible to set an Outgoing Idoc to a red/error state if the RFC transfer fails?
Thanks in advance & best regards,
Alex

Hi,
>>>Is it possible to set an Outgoing Idoc to a red/error state if the RFC transfer fails?
sure it's possible - the IDOC is called ALEAUD and it can tell you the status of the IDOCs in ERP (red etc.)
Regards,
Michal Krawczyk

KUNNR in IDOC COND_A

High,
I have some problems with sending conditions to the other systems. I have to send the condition which is relevant for only one customer. I have tabel with SO/DC/Customer (KUNNR) only. When I send the condition out via VK11 --> conrition info --> send condition, outgoing IDOC is created, but KUNNR field is not filled. KUNNR field is in IDOC documentation (WE60) and should be filled. What I have to do, to get customer number to the standard KUNNR field.
Thanks,
BR, Matija

Hi,
I checked in the customizing ant I have this in my table
Field name Data element Domain name
KUNAG KUNAG KUNNR
As I can understand you, there is something wrong with that?
BR, Matija

Populating retransmission data in QALITY02 IDOC

Hi,
In transaction code QC22, there is no option provided for retransmission. We are using IDOC QALITY02 to transmit the COA data to one of our customers. We would like to provide an option for the users to select retransmission (like in transaction code QC20), and would like to capture the retransmission status data in the outgoing IDOC.
Is there any user-exist available to resolve this requirement? Or any other method that needs to be used?
I appreciate your feed back.
Thanks and regards,
Shiva

No response, hence closed.

No WPDNAC outgoing IDoc is generted

Similar Messages

Maybe you are looking for