GR and GI posting IDOC

Hi,
I need to post GR and GI posting at a same time. I am using MBGMCR message type. Posting is happening properly. But i need to map the material codes in line item to local material codes before postind.
Can anybody suggest any user exit.
I have also scene the message type WMMBXY, i think this can be used only for one type posting at one time either GI or GR. Please help me

Hi Neha,
If you are using ECC 6.0, then look for some spots and try changing the values in runtime.
If the changed values reflect in table, then find a spot there and write the code.
You can try an enhancement spot in include LMIGOKD1
check EXIT_SAPMM07M_001
check BADI MB_MIGO_BADI
Manas M.

Similar Messages

Delivery and Shipments for idocs posting

Hi
- warehouse shipment advice (EDI 945) related (to update qties, packing info, and post G/I)
can i use DELVRY01 or DELVRY02. . which one for what.
- customer ASN (EDI 856) related - SHPMNT01 to SHPMNT03
will it update delivery
& also the shipment document

Hi there,
as its quite a bit of work to find out which fields to fill when posting idocs, here is an example idoc that updates LE shipments and does a shipment completion:
Message Type SHPMNT Basic Type: SHPMNT05
Segment     Field     Description                                                                                Sample
E1EDT20     TKNUM     Shipment Number                                                                   1101933359
E1EDT20     EXTI1            Shipment External reference                                              1101933359
E1EDT18     QUALF     Qualifier                                                                                CHA3%
E1EDT18     PARAM     3% (Means that all fields that are filled in the idoc shall be changed. others unchanged.
E1EDT10     QUALF     To indicate that the sap must do a shipment completion     004
Repeat segment if you need to do other things
E1EDT10     IEDD     Shipment completion end date                                               20110926
E1EDT10     IEDZ     Shipment completion end time                                               101344
E1EDT20     VBELN     Delivery number (with leading zeroes 10 digits)                          0083127938
E1EDL24     POSNR     Item Number (with leading zeroes 6 digits)                          000001
E1EDL24     MATNR     Material Number (with leading zeroes 18 digits)                          000000000000450931
E1EDL24     WERKS     Plant                                                                                74A7
E1EDL24     LGORT     Storage location                                                                     POLC
E1EDL24     CHARG     Batch number                                                                     LOLO

Error while posting idoc in the receiving system.

i have processed idoc in the same system( sending and receiving idoc in the same system ) by creating a dummy logical sys and uploading a text file for customer details.The outbound processing is succesful and it shows a status message 3. But duriing the inbound processing it shows status as 51 with error as 'ENTER VALID VALUE'. but when testing using we19 it is posted sucessfully without any error..is there anything that i have to configure to process inbound idoc sucessfully?? can any suggest me the correct method for doing this.. suggestions please..
thanks
vidya sagar

Hi,
you need to make sure that in WE20 inbound processing parameters for you LS is maintained propperly. You need to give correct function module and enter whether IDoc should be processed immediately or IDocs should be collected and processed as batch. Also you may check whether the distribution model (BD64) is maintained correctly for the specific message type in the system for inbound processing.
Regards,
Kai

SM 58 error while posting Idoc

Hi
I have installed a Netweaver XI 7.0 recently and have completed postinstallation tasks.
Communication between all XI components (i.e IR, ID and SLD is working.)
I am trying to test an Idoc to File scenario and while posting an Idoc from my R/3 system I am hitting upon this error "No service for system SAPD46, client 800 in Integration Directory".
I have scanned SDN forums and came across note 940313 which talks about the registration of R/3 system on SLD by one of the two methods as below..
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
      Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
      SLD (Business system):
      You can now explicitly assign a business system to this client.
      For more details, refer to the SLD documentation.
      Activities in system ABC (self-registration in the SLD):
      Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
      In system ABC, you can check your configuration with Transaction SLDCHECK.
      Activities in Integration Directory (import business system from SLD):
      You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
      Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
I have performed activities highlighted in BOLD. But still error is same.
My question from XI Gurus is that is there any way to know if the manual step of registering my R/3 system in SLD is sufficient (As the SLD bridge for my R/3 system is not configured and I can not use auto registartion.)
Is there any way to check if the R/3 system is successfully registered.
Thanx
Lovein
Edited by: Lovein Khullar on Sep 17, 2008 11:16 AM

Hi,
I think it is due to basis problem, at ID one of service is not working. Please check below mention link for configuration steps
http://help.sap.com/bp_bpmv130/Documentation/Installation/Configuration_Guide_FP.pdf
Meanwhile check all authorization for IDOC processing, else can't process idoc in XI
For IDOC to FILE scenario follow below steps
1. Define Logical system through BD54 after that assign logical system to client through SCC4 window in R3 & XI systems
2. Define RFC destination through SM59 window in R3 & XI
3. Define Port & partner profile through WE21, WE20 windows
4. Trigger idoc from transaction code or test window through WE19.
5. In XI configure SLD under define Product, Component, Technical & business system, it should be WEB as ABAP type.
6. Import component from SLD to ID window meanwhile import idoc from R3
7. Define target structure according to ur requirement and map accordingly
8. Define ports IDX1 & IDX2 in XI
9. In ID define scenario under import business system and configure steps according to ur requirement. Here IDOC is sender so no need communication channel and sender agreement.
It will work without fail

Error when posting IDoc *** in system ERP100

Hi Experts!
Can you pls help me with a goods receipt issue?
When user tries to make a good receipt on a PO, we have the msg "Error when posting IDoc *** in system ERP100" in SRM front-end application monitor.
The same msg is getting displayed in RZ20.
On the idoc itself in tcode WE02 however, I can't see any problem and unfortunately I have no access to the same t-code in R/3. Anyway, I don't see the GR on the PO.
What can be the reason for this problem please?
What is in general the way to analyse and solve this kind of issue?
Thanks a lot !!
imre

Hi,
First find out the PO number from the idoc in tx WE02 in SRM system. Then in ERP , transaction BD87 , specify the details like message type and the system information .... and find out the PO that was errored out for GR. From this we can find the cause of the error. First try to rectify the error and then run the report to clear the contents of BBP_DOCUMENT_TAB.
Hope this helps.
Regards,
Kalyan

XI unable to post IDOC to ECC the interface is FILE-to-IDOC scenario

Hi All,
The XI interface is a FILE-2-IDOC scenario and some times IDOC's in the receiver system are not posted. I did see successfully message for that particular messages but the IDOC's were not created in the ECC. If the messages is reprocessed then IDOC's are posted successfully to the ECC system. The message has checkered flag in the SXMB_MONI tcode.
This issue is occurring intermittently so could some point me in the right direction how to trouble shoot the issue.
Thanks,
Sarvesh

Hi,
Interesting problem...since its intermittant..
You cannot use any of the traditional RWB or message monitoring or cc chanel monitoring here as the error is in the ecc system, so from an XI standpoint it has left XI succssfully..that explains all the chequered flags..indicating success.
we19, we12, we14(process all idocs) test out the whole process with a load..use transaction we46..this can tell you why it is failing....in r/3
from the ecc system to check inbound queue monitoring.
from there you can select the IDocs or queues which you want to monitor, using the specified selection parameters available.
Look at the status record for the idoc that should give you more information, processing status of the idoc...that should tell you the status code assigned to it..
There is one other option here....if you can figure out what sequence they need to be posted in...that might be the reason for the failure..you can specify the sequence to post the idocs in, use qRfc ..
Hope that helps
Regards
Ravi Raman

Help Required to post IDOC from R/3 to XI

Hello,
I need help to post IDOC from R/3 to XI
My XI System --- E11 on client 001
My R/3 System -- IXS on client 812
In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 )
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS )
While Posting data from R/3
Recipient Port --- A00020
Recipient Partner No -- RECE
Recipient Partner Type --- LS
Sender Port --- SAPB6M
Sender Partner Number -- B6MTEST
Sender Partner Type --- LS
I am getting error " Could not post IDOC to R/3".
Please let me know where are my setting are incorrect
Regards

In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 ) ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS ) ( Not require in SAP XI)
chenage the PORT NAME IN R/3 it should work.

Authorization error in posting IDoc

Hi,
I have completed configuration of File to IDoc scenario. When File adapter has picked up the file from FTP server, the message is processed with outbound error.
To find out the error occured at the outbound side, I ran the transaction 'SM58' which explained that XIAFUSER does not have authorizations to post the IDoc to destination system. Can somebody provide what authorizations should be given to this user to facilitate the processing of message.
In another instance the same error has resulted but notifying the different user. This time WF-BATCH does not have authorizations to post the IDoc to destination system.
As per my understanding there should be some system configuration where you have an option of specifying the user for posting IDocs to destination system.
Please confirm whether my understanding is correct and also let me know the where it is done?
Regards,
Suraj

Hi Suraj,
The user id which you are using in your RFC destination will be of your target system to login. This user id should be having all SAP_ALL authorizations attached into their profile.
Pls do try with the help of your basis by assigning this profile to your WF-BATCH user.
Cheers
JK

Populating Street2 and Street3 through Idoc CREMAS

Hi
Is there a way to populate the fields Street2 and Street3 while creating a vendor through the idoc CREMAS05?
Thanks
Nag

Look for an exit when posting IDOC and use this to populate any additional fields.
Try ACCID001, ACCID002 or search for BADIS.

How to post idoc ORDERS05 from ABAP standalone program to the same R3 syst?

Hi Masterminds,
I need to post IDoc from ECC to same R/3 system. For that i need to develop a standalone program which will post Idoc 'ORDERS05'.
I had the following data:
E1EDKA1                         - PARTN
E1EDK02; QUALF = 001        - BELNR
E1EDP19; QUALF = 003     - IDTNR
E1EDP02; QUALF = 997        - BELNR
E1EDP01     MENGE               - Space
E1EDP02; QUALF = 999        - BELNR
E1EDK01     BSART               - Space
E1EDP19; QUALF = 002        - IDTNR
E1EDP01     ABGRU              - Space
E1EDKA1     PARVW              - Space
Please provide me details how to write the program and what necessary steps do i need to follow.
Thanks......

Hi,
Do ALE settings and Fill two tables of type EDIDD and structure of type EDIDC
and pass it to function module
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL                  = P_WA_EDIDC
OBJ_TYPE                                              = ''
CHNUM                                                   = ''
    TABLES
      COMMUNICATION_IDOC_CONTROL           = P_I_EDIDC
      MASTER_IDOC_DATA                                = P_I_EDIDD
   EXCEPTIONS
     ERROR_IN_IDOC_CONTROL                        = 1
     ERROR_WRITING_IDOC_STATUS               = 2
     ERROR_IN_IDOC_DATA                              = 3
     SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
     OTHERS                                                            = 5.

What authorization required to post idoc from XI via RFC?

Hi all,
I need to post idoc to SAP R/3 system from XI. I have done all the steps correctly. While creating RFC in XI system to connect to the R/3 system, intially I gave my R/3 username and password and tested teh connection. Everything was working fine but when I actually ran the scenario, IDOC was not getting posted in the R/3. But there was no error anywhere.
fianlly after debugging I fould it might be the issue of authorization the the R/3 user i used in the RFC. I then assigned SAP_ALL authorization to my user and posted the iodc again and it started working fine.
Can anyone please tell me what are th exact authorizations/role i need to assign to the r/3 used to use it in RFC and successfully posting the idoc? I dont want to use SAP_ALL authorization in my production environemnt.
Please help.
Regards,
Yash

Hi,
Even i had faced this problem. Whenever I tried to send IDOCs, i used to get an error in SM58, " No authorization to send IDOC of type DEBMDM".
When i got SAP_ALL it worked. However I raised a note with SAP asking for an alternative and this is the reply gave me.
You can get good information on this topic in your online help files.
The following is taken from the document "General Security Measures
(ALE)":
Use the transaction SALE to maintain the ALE configuration, to include setting up the distribution model and setting up ALE user authorizations and profiles. Note the following:
- Be restrictive when assigning the ALE authorizations.
The authorization profile B_ALE_ALL contains the following
authorization objects that are needed for ALE:
Authorizations for ALE
Authorization Description
B_ALE_CGRP ALE Customizing Distribution: Group Activities
B_ALE_LSYS ALE/EDI: Maintaining logical systems
B_ALE_MAST ALE/EDI: Distributing master data
B_ALE_MODL ALE/EDI: Maintaining customer distribution model
B_ALE_RECV ALE/EDI: Receiving IDocs via RFC
B_ALE_REDU ALE/EDI: Generating messages (ex. reduction)
S_PROGRAM ABAP: Program run checks
S_TABU_DIS Table Maintenance (using standard tools such as SM30)
Protect external users and passwords.
For example, for a non-SAP system to send IDocs to a SAP System using transactional RFC, it must also send a SAP user ID and password.
In most cases, the user and password are stored outside of the SAP System. Make sure that this information is not accessible to external systems or programs. (How you can do this is dependent on the system that you have; therefore, you need to refer to the documentation for the system where the information is stored.)
However, I feel assigining the profile S_IDOC_ALL should also be enough. Just try and see.
Regards,
Merrilly

While Posting IDOC from XI to R/3 Message Type needs to be changed

We are doing mapping IN XI. For one condition we want Message Type to be ORDERS and for one condition we want Message Type to be ORDERSCHG
when posting IDOC from XI to R/3.
Pls revert anybody asap.
Regards

Hi,
>>>>It means I need to create two Interface Mappings for the same message mapping and then I can use the Interface Determination . Am I right.
no, you need two message mapping
and two interface mappings
file - orders.orders05
file - ordrchg.order05
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Posting IDOCs with partner type SP ?

We have to post IDOCs to SAP where the partner type is SP . How do we configure XI to achieve this ?
We are disabling the control record and so not looking at the option of hardcoding the EDI_DC record.
I understand we need to specify Alternate identifiers in IDOC channel and also choose header mapping in receiver agreement, however am not very clear on the steps.
Can neone help me with the steps.
Thanks
Saravana

I need values something like below to be in the control record of the IDOC and could not find a way of doing it
<SNDPOR>PORT1</SNDPOR>
<SNDPRT>SP</SNDPRT>
<SNDPRN>ServiceProvider1</SNDPRN>
<RCVPOR>SAPS32</RCVPOR>
<RCVPRT>SP</RCVPRT>
<RCVPRN>ServiceProvider2</RCVPRN>
By default , the SNDPRT & RCVPRT carry the constant "LS"(i still do not get y this is enforced by the IDOC adapter). Our sender system is a FTP server & receiever is SAP system. We have the Business Systems defined as service without party.
I tried hardcoding the values in EDI_DC40 in message mapping, but the IDOC adapter removes(!!) it and creates its own header(inspite of the chk box being unchecked or checked!!?? in the communication channel configuration)
Christoph , i could not make out much out of the thread u ve pointed to.
Thanks
Saravana

Error posting Idocs

Hello,
I am working on sending idocs from XI to SAP R/3. While posting idocs from XI to R/3 i am getting errors on outbound side in SM58 and IDX5.
In XI it says -
Function Module:
IDOC_INBOUND_ASYNCHRONOUS
Error Text:
No authorization to send IDOCS of message type HRMD_A
I checked authorizations and granted SAP_ALL and SAP_NEW to the extraction user but still same problem.
Best Regards,
Sudheer

Hi Sudheer
First Check This
Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
Incase All this are proper
delete metatdata in IDX2 And reimport the same.
Also Check This
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Abhishek Mahajan

How to post idoc from r/3 to xi

hi experts i have one doubt abt posting idoc from r/3 to xi
how to post
for vendor master idoc
for sales order idoc
for purchase order idoc
for delivery idoc
is there any inbuilt posting prgms r there or we have to write the prms.
please clear me
regards
babu

to add more...
Befor posting IDOCS into XI..we need to do ALE SETTINGS...as fallows..
ALE settings.
SAP XI1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
and coming to the posting, u can go with WE19

GR and GI posting IDOC

Similar Messages

Maybe you are looking for