Need to send BOM material in Idoc WMMBXY - WMMBID02

Hi All,
I have a requirement, the inbound GR gets posted into SAP from third party system, here they will send the BOM details with the main material. Pls let me know which segment the BOM value can be passed? so that the GR gets posted with BOM components.
Pls note, If I send the main material from Idoc the component are picked from SAP and the GR posted with BOm components. My requirement is, If the BOM qty changes the will send the BOM and new qtys. I need to post the GR with the new BOM qty.
Thanks in Advance.

Hi Pavithra,
How to Guide for sending mails:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0964d7c-e66e-2910-24bb-ac535e4a5992
Use StrictXML2PlainBean in the module processor to convert the data to CSV:
/people/pooja.pandey/blog/2009/02/23/xml-to-text-conversion-made-easy-by-strictxml2plainbean
http://help.sap.com/saphelp_nwpi711/helpdata/en/44/748d595dab6fb5e10000000a155369/content.htm
Regards,
Aravind

Similar Messages

Goods receipt - IDOC (WMMBXY/WMMBID02) error

I am creating an inbound goods receipt with IDOC WMMBID02 and get the error 'Document date / / is incorrect in item 0000000001'. Error code: F5833.
Error Diagnosis: 'Service financial accounting: document date " / /" is technically incorrect in item "0000000001" of the accounting document.'
Anyone know why I get this error. Appears to be FI related.

Hi,
The error occurs in the following function module:
CALL FUNCTION 'DATE_CHECK_PLAUSIBILITY'
       EXPORTING
            DATE                      = I_BLDAT
       EXCEPTIONS
            PLAUSIBILITY_CHECK_FAILED = 01.
CHECK NOT SY-SUBRC IS INITIAL.
MESSAGE E833 WITH I_BLDAT I_POSNR.
Please check the documentation for the function module for details.
regards
Aveek

Inbound Goods receipt - IDOC WMMBXY/WMMBID02

I am able to post a GR with WMMBID02, but the status msg 53 only says 'Application document posted'. Why does it not provide the document number in message?

Hi,
You need to do this programitically. For ex:
PERFORM idoc_status_fill USING c_idoc_status_ok_incomplete
                                                           v_idoc_docnum
                                                               c_success
                                                                    c_id
                                                                    44
                                                      struct_emkpf-mblnr
                                                      struct_emkpf-mjahr
                                                                   space
                                                                   space
                                                      p_i_tab_step-fname
                                                                   space
                                                                   space
FORM idoc_status_fill USING value(status)
                            value(docnum)
                            value(msgty)
                            value(msgid)
                            value(msgno)
                            value(msgv1)
                            value(msgv2)
                            value(msgv3)
                            value(msgv4)
                            value(routid)
                            value(segnum)
                            value(segfld).
i_idoc_status-uname = sy-uname.
i_idoc_status-status = status.
i_idoc_status-docnum = docnum.
i_idoc_status-msgid = msgid.
i_idoc_status-msgno = msgno.
i_idoc_status-msgty = msgty.
i_idoc_status-msgv1 = msgv1.
i_idoc_status-msgv2 = msgv2.
i_idoc_status-msgv3 = msgv3.
i_idoc_status-msgv4 = msgv4.
i_idoc_status-segnum = segnum.
i_idoc_status-segfld = segfld.
i_idoc_status-repid = sy-repid.
i_idoc_status-routid = routid.
APPEND i_idoc_status.
CLEAR i_idoc_status.
ENDFORM.                    " idoc_status_fill

Error while sending Material Master IDOC to Auto ID 2.1

Hello All,
I am using Auto ID 2.1 with SP1 on NW04.
Integration server is XI 3.0 with corresponding XI Content for Auto ID.
The backend is ERP2004.
I am using the config guide for Auto ID 2.1.
After completing the configuration, I tried sending the Material Master IDOC to Auto ID.
IDOC gets created successfully. XI says the message transfer is successfully.
In the log of Auto ID. I am getting the following error while importing the Material Master product:
Product ID AUTOIDAII_MAT has an invalid format
Internal error in /AIN/DM_PROD_COMMIT
Message no. COM_PRODUCT897
The description says that it may be a program error.
Or the program expects some variable to be filled which has not occured.
Any idea what could be the error. Or where should I try looking for to get more detail info.
Do some one knows what should be the patch levels for the different components in all three servers for Auto ID 2.1 SP1.
Thanks for any kind of input.
Regards,
Arundeep Singh

HI Arundeep,
use the following
1) XI 3.0 SP level 12
2) AII 2.1 SP2
3) check in rfid outbound configuration guide for any customising for product to be done in AII
regards,
ashit singh

Error while sending Material Master IDOC to Auto ID

Hello All,
I am using Auto ID 4.0 on NW04s.
The backend is ERP2005.
I am trying scenario from RFID-Enabled Outbound Processing - Conf Guide (SAP AII 4.0)
After completing the configuration on the backend, I tried sending the Material Master IDOC to Auto ID.
I get a message that IDOC is just being created. I could not find it in the transaction WE02.
Also, they are not appearing in the AII system.
Thanks for any kind of input.
Regards,
Message was edited by:
Rahul Gavande

Hi Rahul,
I have not worked on these version of products. And I don't know what changes have been done in the new versions.
But still, can you let me know, what is the exact configuration that you have done and also
which partner are you trying to send the IDOC. And if you are trying to send the IDOC then I will suggest to debug the transaction and see till what level it proceeds.
Best of luck,
Arundeep

Error while creatting the Material Master IDOC in ERP 2005

Hello All,
I am trying to create scenario from RFID-Enabled Outbound Processing - Conf Guide (SAP AII 4.0).
I am using Auto ID 4.0 on a NW04s system. The backend is a ERP2005 system.
The scenario requires that I need to create a material in the backend and send it to the NW04s system using IDOCs.
After completing the configuration on the backend, I tried sending the Material Master IDOC to Auto ID from the transaction AIDMM. I get a message that IDOC is just being created. But I could not find it in the transaction WE02.
On debugging I found that the function MARD_GENERIC_READ_MATNR_PLANT resulted in error.
Thanks for any kind of input.
Regards,
Rahul
Message was edited by:
Rahul Gavande

Dear,
Check ABAPer for file settings.
- CANNOT_SKIP_ATTRIBUTE_RECORD : The attributes could not be read in the EPS parcel. The file cannot be opened for reading, because it may have been deleted in the meantime.
- CANNOT_DETERMINE_EPS_PARCEL : The EPS parcel is not in the EPS Inbox, because it may have been deleted. You must download the relevant patch again (for example, Hot Package).
- CANNOT_DETERMINE_DATA_FILES : The name of a data file could not be determined, because a profile parameter was not correctly configured. Check the settings using the report RSPARAM.
- CANNOT_DISASSEMBLE_R_DATA_FILE : An R3trans data file could not be unpacked. A possible error source is that the relevant EPS parcel was not found. The data file could not be opened for writing. An error occurred when transmitting a 20K block from the EPS Inbox to the directory /usr/sap/trans/data (UNIX).
- CANNOT_DISASSEMBLE_D_DATA_FILE : An ADO data file could not be unpacked. The reasons are the same as with the message CANNOT_DISASSEMBLE_R_DATA_FILE .
- CANNOT_CREATE_COFILE : The cofile could not be created from the relevant data file. One possible error source is that <sys>adm does not have write authorization for the directory /usr/sap/trans/cofiles (UNIX).
Check Note: 70752.
Regards,
Syed Hussain.

Trigger an outbound idoc to sender system after inbound idoc has status 53

Hi all,
We have two different partners (say A and B)which send inbound idoc to ECC of same message type WMMBXY. This updates goods movement. The partner A collects the idocs(WE20 partner profile setting) and partner B trigger's immediately. Now our requirement is after successful processing of idocs (satus 53) we need to send another type of idocs to the sender regarding the updation/ changes occured in ECC.
Since partner A collects the idocs how can we check that it reaches 53 status and send the outbound idoc to A.
Kindly help me in solving this issue.
Thanks,
Aravind

Create a new process code WMMB to ZMMB & assign a FM ZL_IDOC_INPUT_WMMBXY
& call the standard FM L_IDOC_INPUT_WMMBXY , check the status or any error other wise create a new IDOC using
Master_IDOC_CREATE, hope the solution works for you

Configuration of material master idoc interface to RFID

Hi,
We are planning to have SAP RFID. Once operational, do we need to send SAP Material Master field data to RFID? For ex; when the description of a material is changed, do we need to send this new information to RFID system through Idoc (or some other way)?
Regards

Yes. This is available in SAP AII which is configurable. Material Idoc is the best way. Activate change pointers generally (Customizing for Logistics - General -> Supply Chain Planning Interfaces (SCPI) -> Auto-ID Backend Integration --> IDoc Processing --> Material Master Data IDocs -> Activate Change Pointers Generally).
Hope this helps.
Thanks,
Naveen

Can we send attach with Inbound IDoc

Hi All,
I have requirement, Proxy to Idoc scenario where i need to send attchement along with Idoc message coming from proxy message. Can we do that?
Also, i have another requirement as , i have 2 receivers , one is soap and one is Idoc , i need to send payload to Idoc reciever and just attachment to SOAP which is coming from Proxy message. How to do this.
Please let me know. Thanks.
Vishal

HI Vishal
You cannot send attachment to IDOC but for SOAP you can.
Attachment from proxy cannot be accessed in mappings and has to be handled as attachment.
Thanks
Gaurav

IDOC WMMBXY outbound - R3 idoc posting error

Hi! All
In a file(inbound) to IDOC scenario using the IDOC WMMBXY.WMMBID02(outbound), i have the following status notification and status grouping is also in red when the idoc is posted to R3...
IDOC: 0000000000605076 Status: Application document not posted
Qty and / or "delivery completed" ind. or final issue ind. are missing
It would be very helpful, if you can let me know ...what i did wrong in the mapping/design.
Thank you,
Patrick

Jones,
The error states:
Qty and / or "delivery completed" ind. or final issue ind. are missing
So please check in the idoc whether you are passing the values for Qty and "delivery completed" or final issue ind. I think to post into R3 you need to have these values.
Regards,
---Satish

Pls send material for idocs in ECC 6.0

Pls send material for idocs in ECC6.0

Hi sitaram s ,
IDoc
- IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful

How to send a Material Idoc in format XML to SQL Server DB?

Hi,
I am creating a Material Idoc in format XML and I need send the same to a SQL Server DB.
In the transaction BD10 I create the XML Idoc, but the same is stored in the SAP Server and I need send this to an external SQL Server DB.
Somebody knows how to send automatically the XML Idoc to a SQL Server DB?
Thanks and regards!
Edited by: marcosap on Nov 11, 2010 4:00 PM

Hi,
All your XML idoc will get store in App layer,you can ask your Unix expert to write the unix code to fetch these XML idoc files and transfer to destination based on time period set by conjob.
This is simple & easy job for any UNIX expert.
Regards
Siva

Issues with creating and sending BOM XML IDOC to SAP using 2010 WCF-SAP Adapter (without using Biztalk Server)

I'm trying to replace an existing Biztalk 2006 Send BOM IDOC process, and completely remove Biztalk server from the equation. The existing Bizatalk 2006 server receives an input BOM (Bill of Materials) flat file, and using a Biztalk Map (BM08),
and Orchestration, generates an Idoc and sends it to SAP.
In my replacement C# program, I'm using the 2010 WCF-SAP Adapter, and am trying to generate the BOMMAT03 XML IDOC it to SAP.
I generated the BOMMAT03 schema from SAP using the Add Adapter Service in VS 2010. I was able to generate a BM08 XSLT from the existing BMO8 map in the current Biztalk 2006 process. I am able to run a XSLT transform on the input BOM flat
file, and generate an XML file from that.
However, I've run into a few issues. First of which, is that the XML file that is generated from the XSLT transform is NOT the same schema as the BOMMAT03 schema expects. It's somewhat similar, but different enough that I have to manually
translate between the two in my code. I've verified that both the original Bitztalk 2006 process and my replacement program use BOMMAT V3 from SAP. Question--Is Biztalk 2006 server doing some other magic to turn that transormed XML into the BOMMAT03
schema?
I ended writing code which translates the transformed XML into the BOMMAT03 schema (which is a strong typed XML IDOC at this point).
However, when I try to send the BOMMAT03 XML IDOC, I get an exception "Object reference not set to an instance of an object."
idocClient.Send(idocData, ref sadapterTxGuid);
idocData is of type BOMMAT03, and I've verified that the various fields are populated.
Any help is appreciated.

Well, putting in a MSDN subscription support ticket for Biztalk server actually helped with the issue. They didn't find, or fix the issue directly. But one of the examples (https://randypaulo.wordpress.com/tag/idoc/) they sent over, jogged my
memory, and I realized in the code snippet below, I had accidentally deleted the 1st line. Such a simple mistake, yet was easy to overlook. The URL example is almost EXACTLY like my code, but without the transform and translation code to convert
from input XML file to IDOC XML. If someone is interested in that, let me know.
//Forgot the 1st line.
idocClient = new IdocBOMMAT03SIEIS_WED_BOMMAT03V3R700Client(binding, endpointAddress);
idocClient.Send(idocData, ref sadapterTxGuid);
For anyone else interested in knowing, you CAN send a strongly typed IDOC to SAP using C#.NET and the WCF SAP 2010 Adapter, using the IDOC Binding Client class you generated using the Add Adapter Service Reference in VS2010.
The one difference, which no one, not even the tech support from MS could tell me, was why the XSLT which I generated from the original map, did not transform the input BOM XML into the BOMMAT03 XML. Instead, it transformed it into an intermediate
XML, which resembled the BOMMAT03 IDOC XML, but still needed to be translated to the BOMMAT03 IDOC format.
The tech support person swore up and down that it should. But I believe that something happens in Biztalk server, after the Mapping occurs, maybe in the Pipeline, which converts that
intermediate XML into the final BOMMAT03 IDOC XML format.
I do think that the examples are severely lacking in showing how to send a strong typed IDOC using C# and the WCF-SAP Adapter. Even worse, the examples are completely lacking in how to actually generate a weakly typed IDOC. They show how to send
that weakly typed IDOC, but show me, or give me a class to be able to generate it.
I realize that this is not quite the "recommended way" to do it, but in reality, not everyone wants or even needs a full Biztalk installation. For some simple stuff like this, a C#.NET program and WCF-SAP adapter do the trick.

Do we need a sender channel for IDOC to file scenario.

Hi,
Do we need a sender channel in IDOC to FILE scenario.
Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
What is the reason for this?
Regards,
Younus

Younus,
to add more...
From WAS(Web Application Server) 6.20 and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
And it has got ABAP and JAVA engine in it.
It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.

The SAP Web AS 6.10 did not have a Java engine.
and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
Hope i cleared ur point...
Cheers,
Raghavesh
Message was edited by:
Raghavesh Reddy

All Line Items need to send in the PO Change EDI IDoC - ORDCHG

Hi EDI Experts ,
We have ECC 6.04.
We are sending PO Change Message Tyep by using Message Type ORDCHG ( Basic Type ORDERS05)
If PO Changes system trigger IDoc and in Std IDoc it displays only that Line Item who had been changed .
Requierment is that if there is change in any single item, then sytem should send entire/whole PO document ( all Line Items) .
I think we need to write some code in teh routine /requierment ...etc.
Can anyone suggest what I need to do to acehive the above ?
Thanks
NAP

Hello NAP ,
I have the same problem that you. I ´m using the message type ORDCHG with basic type ORDERS05. when sending change order through Idoc only show me the updete/delete Item in segnment E1EDP01.
What object did you use for the message type ORDCHG ?
What settings should I consider for this?
Thanks in advance,
Luis.-

Need to send BOM material in Idoc WMMBXY - WMMBID02

Similar Messages

Maybe you are looking for