PassingCustomer Address in IDOC

Hi gurus,
Requirement is to pass Address IDOC along with customer IDOC DEBMAS06.
For DEBMAS06 i have already done change pointer settings and it is working fine.
What should i do for triggering Address IDOC (message type ADRMAS,ADR2MAS,ADR3MAS)
Regards,
Madan Gopal Sharma

Activate change pointers via BD50 and this for all 3 message types. (ADRMAS)
Link change documents to change pointers via BD52, and this for all fields (don t forget the KEY-fields)
example :
ADRESSE       ADR10     ADDRNUMBER
ADRESSE       ADR10     CONSNUMBER
ADRESSE       ADR10     KEY
and so on...

Similar Messages

Vendor email address in IDOC

We are trying to create a vendor payment file to be sent to our bank in IDOC format. The IDOC type we are using is PEXR2002. We are not able to populate the vendor email address (from vendor master data - SMTP_ADDR) into IDOC segment E1EDKA1 even though the email address is shown on the vendor master. All other vendor master address information, such as Phone, Fax, show up correctly in that segment. Does anybody know how we can populate the IDOC with the email address?
Thank you.

Thanks, Ravi. We are trying to avoid creating a user exit and since all the other vendor info populates the IDOC correctly, we're hoping there's a 'standard' way of getting the email there as well.

Recieving IDOC's from SAP

Hi Forum,
In a scenario where SAP sends IDOC's to xMII, what should be the best landscape ?
Do we need to have both xMII and SAP ECC installed on same machine ?
I configured a RFC destination in SAP and i don't see any place where one can mention about the DESTINATION xMII server's address. IDOC's are directed to xMII which is installed on the same machine as SAP server.
Mike.

Hi.
We are just in the middle of doing something similar. Have you been through these docs ??
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/201769e0-3174-2910-e287-baa58d198246
and
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
Our landscape is to send IDocs from a central SAP server to a local xMII server at the production site.
Hopefully of some help.
BR
Poul.

ALE - Idoc not getting processed automatically, instead going fine in Debug

Hello All,
I have a problem with Inbound idoc processing.
IDoc settings were made 'immediate processing' in WE20, and the process code is set correctly and the attached of Z-Fun. module to process the idocs to process code.
The error in inbound side is as 'Function module not allowed: APPL_IDOC_INPUTI' 51 status. Am sure i have to do some thing with ALE settings.
Can some body help me with correction step or sequence of steps for this ALE process.
Thanks & Regards, Jilan

Hi Jilan,
Plz follow the steps:
ALE Configuration:
     WE30 - IDOC type creation
     WE31 - Create segment
     WE81 - Message type creation
     WE82 - Link IDOC type to Message type
     SE37   - Create Inbound Function Module
     BD51 - Maintain entry for Function Module
     WE57 - Maintain
     BD57 - Link Function Module, IDOC type and Message type
     WE42 Create Inbound Process Code
     BD67 - Link Process code to Function Module
     WE20 - Create Partner Profile
     BD64 - Display Distribution Model
     WE02 - IDoc List, Display all Inbound/Outbound IDocs
     WE14 - Outbound Processing of IDocs
     BD20 - Inbound Processing of IDocs
1st Step:   Create a Segment ( WE31)
         Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
         Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step:   Create IDOC Type ( WE30 )
        After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
       Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
       Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step:   Create Message Type (WE81)
     Message Type is like the Postman for sending the Letter.
4th Step:   Attach Message Type to the IDOC Type (WE82)
5th Step:   Create a Function Module (SE37)
       Write the Processing logic in a Function Module.
6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step:   Create a Custom Process Code (WE42)
9th Step:   Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
reward is useful,
regards,
Tanmay

IDOCs for PO Change

Hi SAP Gurus,
I am very new to SAP IDOCs & I have requirement related to IDOCs and which may be a simpler one for many but Im finding it difficult as I am new to it.
The requirement is, whenever a PO is changed it should send out a IDOC to replicate those changes in another PO which would be in another system.
Whenever there is change in delivery quantity & delivery address, this IDOC should be triggered.
I am okay with the O/P determination part and can handle that but need help in partner profile & other areas, and my first area of concern is the basic type.
I checked in WE30 for basic types(related to PO change) ORDERS04/PORDCH01 but couldn't find an appropriate segment to send out the data. Can you pls explain how to handle this.
Also, shall we consider IDOC Basic type extension as an option??
Your inputs are highly appreciated..
Thanks

Hello ,
you can use the IDOCBasic type extension to meet this functionality and check with your ABAPER to get this done.

W to read the idoc in inbound

HI Freinds
              I am new to idocs...I have created (custom)idoc using stand alone program in outbound.....then what are the next steps in inbound....if we have to create process code in inbound side....how to read idocs and post the inbound...pls any body tel me clearly....
Regards
Mani R

Hi mani,
You should follow the following steps 1 by 1.
     WE30 - IDOC type creation
     WE31 - Create segment
     WE81 - Message type creation
     WE82 - Link IDOC type to Message type
     SE37   - Create Inbound Function Module
     BD51 - Maintain entry for Function Module
     WE57 - Maintain
     BD57 - Link Function Module, IDOC type and Message type
     WE42 Create Inbound Process Code
     BD67 - Link Process code to Function Module
     WE20 - Create Partner Profile
     BD64 - Display Distribution Model
     WE02 - IDoc List, Display all Inbound/Outbound IDocs
     WE14 - Outbound Processing of IDocs
     BD20 - Inbound Processing of IDocs
1st Step:   Create a Segment ( WE31)
         Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
         Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step:   Create IDOC Type ( WE30 )
        After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
       Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
       Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step:   Create Message Type (WE81)
     Message Type is like the Postman for sending the Letter.
4th Step:   Attach Message Type to the IDOC Type (WE82)
5th Step:   Create a Function Module (SE37)
       Write the Processing logic in a Function Module.
6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step:   Create a Custom Process Code (WE42)
9th Step:   Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
Reward is helpful,
Regards,
Tanmay

Idoc in proxy

Hi,
i want to update the data in idoc,can i do it using proxy?can i use idoc in server proxy?
Regards,
rao

Hi Rao,
yes, you can do that but it will require unnecessary coding effort.
When you already have a idoc its preferable to use idoc..
And if yours is a specific case which cannot be addressed by Idoc or idoc(customizing), then am afraid you are forced to use the proxy.
Hope the answer to you Q.
rgds,
chemz

Handling unit preventing deletion of inbound delivery

Hello,
Our Decentralized WMS had a glitch in the system that left several
idocs queued to create inbound deliveries. These deliveries have
associated handling units which were placed from the outbound delivery
to the inbound. Before the inbound deliveries could be created via XI,
users created manual inbound deliveries against the POs and PGRed.
When the Decent WMS glitch was addressed, the IDOCs submitted were
processed, creating inbounds with handling units that were completely
packed.
So our system contains 2 inbounds for a po. We would like to delete the one with with the handling unit, but it's not that simple.
To address this issue, it is necessary to remove the handling units,
but this isn't possible. We receive an error message, unable to change.
I've attempted to PGR the delivery but this isn't possble either.
the following error message is received.
MSSA-SATRA exceeded by 2 EA : 10004063 AA26 0001 E
How can these Handling units be deleted to allow the associated inbound
deliveries to be deleted as well?
Is there a program to modify the status of the handling unit? I do not
want to perform any table editing or goods movements unless there are
no other alternatives

applying note 1083602 which should resolve

Fixed Length File attachment to Mail Receiver

Hi,
I have an interface requirement IDOC - PI - Fixed Length File attached to email.
Is it possible to do this? I need to pass the IDOC through a mapping and content conversion to build the fixed length file, I then need to attach this file to an email and send it to a user.
Any help would be greatly appreciated.
Thanks
Gareth

Hi,
I actually need to convert the IDOC to a different file format before sending it on. Eg.
<IDOC>
     <Segment 1...n>
           <username>User</username>
           <address>Address 1</Address>
     </Segment>
     <Segment>
           <username>User2</username>
           <address>Address 2</Address>
     </Segment>
<IDOC>
Converted to flat file with structure:
User......Address 1.....
User2....Address 2.....
The file needs to have fields of Fixed Length (thats what the .... after each field is to represent)
So I think the Data Type I am using for the file needs to go through Content Conversion to do this change, and then the file attached to an email.
I hope this makes sense.

URGENT!!!!!!! URGENT!!!!!! ALE

how to design ALE outbound / Inbound setting for distributing master data using service program................PLS.. send me the details to the following mail
[email protected]

Hi Raghavendra,
You should follow the following steps 1 by 1.
WE30 - IDOC type creation
WE31 - Create segment
WE81 - Message type creation
WE82 - Link IDOC type to Message type
SE37 - Create Inbound Function Module
BD51 - Maintain entry for Function Module
WE57 - Maintain
BD57 - Link Function Module, IDOC type and Message type
WE42 Create Inbound Process Code
BD67 - Link Process code to Function Module
WE20 - Create Partner Profile
BD64 - Display Distribution Model
WE02 - IDoc List, Display all Inbound/Outbound IDocs
WE14 - Outbound Processing of IDocs
BD20 - Inbound Processing of IDocs
1st Step: Create a Segment ( WE31)
Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step: Create IDOC Type ( WE30 )
After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step: Create Message Type (WE81)
Message Type is like the Postman for sending the Letter.
4th Step: Attach Message Type to the IDOC Type (WE82)
5th Step: Create a Function Module (SE37)
Write the Processing logic in a Function Module.
6th Step: Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step: Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step: Create a Custom Process Code (WE42)
9th Step: Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
Reward is helpful,
Regards,
Sasi

How to populate address details in IDOC

HI,
I am creating customer master using OILDEB06 IDOC.
However I dont see the fields like SMTP_ADDR, SORT1, Street 5 etc in the idoc segments.
How do I pass all the address details along with my IDOC.
Do I need to use some BAPI or am I missing something inMapping.
Appreciate your help.
Thanks and regards

These are additional address fields which are part of 'Central Address Management'. Pasted below is the documentation associated with it. Basically, you need to add these separately.
<i>
Additional address fields:
There are additional address fields available due to linking the customer and vendor master and the respective contact persons to central address management. This additional address information is stored in central address management's own tables rather than being kept in the actual master tables (KNA1 for the customer master, LFA1 for the vendor master, KNVK for the contact persons).
A separate transfer run via the ALE interface is needed to transfer this additional address information. This run should be before the transfer run for master data.
See Transfer of address data.
If you use number ranges with internal number assignment when creating new customer and vendor masters, the number which is used to identify the master object in the system must be determined beforehand due to address information and master data being transferred separately.
You can determine the numbers using the following BAPIs:
BAPI_VENDOR_GETINTNUMBER (for the vendor master)
BAPI_CUSTOMER_GETINTNUMBER (for the customer master)
BAPI_PARTNEREMPLOYEE_GETINTNUM (for the contact persons)
Master data fields for which there is a counterpart in central address management (such as name, street, or telephone number) continue to be filled in the actual master tables. The formatting for these fields within central address management is different from the original formatting of the fields without the link to central address management. We therefore recommend that you only transfer the data for such fields when transferring central address management address information.</i>
Here is the documentation on transferring address data.
<i>
Transfer address data
You can use the DX Workbench (transaction SXDA) to transfer address data.
Create a transfer project using the following object types:
BUS4001 for company and organization addresses (for example, customer address, vendor address, other office address of contact person)
BUS4002 for private addresses (of contact person)
BUS4003 for office addresses (composite work address of contact person).
The address data is entered by the SAVEREPLICA-BAPIs of these three object types.
For more information about these BAPIs and their interfaces, in particular the meaning of the key fields, see "Distributing addresses via ALE" by choosing Basis --> Basis Services/Communication Interface --> Business Address Services in the SAP Library.
You can create example files for the DX Workbench from existing address records in the system (for example, in a customer master record ) with the programs RSDXBUS4001, RSDXBUS4002 and RSDXBUS4003. These example files show the meaning of all fields in the Business Address Services BAPI interfaces.
The programs have the same input parameters as the SAVEREPLICA-BAPIs.</i>
Please reward and close the post once answered.
Srinivas

PO is getting created but showing error is address with status of IDoc - 51

Hi Experts,
I am using IDoc type - PORDCR103
Process code - copy of IDOC_INPUT_PORDCR1 (Function Module)
After processing through WE19 it is generating an IDoc number with status - 51 showing error in Address , But it is creating a PO.
My requirement is In status -51 It should not create PO.
Inside IDOC_INPUT_PORDCR1 a Bapi 'BAPI_PO_CREATE1' is used for creating PO. Here In RETURN parameter of BAPI a Row is comming with Message type - E. Some other messages are also there of type 'S' and 'W'.
After processing , PO is getting created with staus - 51.
Please help me .
Thanks
Susanta
Edited by: Susanta22 on Oct 11, 2011 12:29 PM

Hi,
in ur code ur filling the idoc data rcord, control record ryt ..before u append data to idoc data , u r also validating and u might be doing in loop for appening the idoc data.
if there is any error in idoc then it won't distribute the data, it will be in error status only..u can only see the data in WE02. Then u can also change the data in WE02 and redistirbute it via BD87.
if u have any conerns let me know
Regards,
Nagaraj

Vendor Master IDOC - Email address

HI,
Requirement is to include email id in outbound vendor master IDOC CREMAS, IDOC only have address number :-(
Any pointers how it can be achieved? preferably without coding
Also how can I include email address in the change pointers as well (BD52)?
Regards,
Manoj Aggarwal

Hi Manoj,
Please go through SAP note 384462 - Master data and addresses
Regards,
Tomek

Vendor Address is not updating in ADRC table by LSMW IDOC method

Hi,
I'm updating Vendor address data by LSMW IDoc method
for this i'm using ADRMAS as msg type and ADRMAS02 as Idoc type.
In partner profiles Process code given as BAPI for this.
i maintained entry in TSADOBJ table LFA1 as OBJTYPE,1 as ADDR TYPE,0001 as context,LFA1 as TABLENAME,ADRNR as FIELDNAME, ADRC as TABLE PERS, ADDRNUMBER as FIELD PERS
Idoc generating sucessfully.
But data is not updating in database.
i think the problem in TSADOBJ config.
Please give exact configuration which can update vendor data.
Thanks in advance

be open minded. SAP gives several import methods to load vendors. one of them is per IDOC.
But the vendor master IDOC does not automatically create the adress master.
And even more important, if you migrate data from one SAP system to another, the IDOC method is more straight forward than the batch input, because you can send the IDOCs from legacy system to new system, you will then have a 1:1 relation of the structure in LSMW and you can create vendor masters by knowing the new vendor number from an internal number range already in LSMW, long before you actually post the vendor. With batch input you can either post with numbers from external number range, or you just dont know the new number already in LSMW.
And you dont need to download the data to Excel. And further, the LFA1 adress data has less information than the ADRC adress data.

ARIBA Integration with SAP (based in iDoc interchange) with deviating "remit-to" addresses for incoming vendor invoices

Hi,
We are currently trying to implement our ARIBA interface for incoming vendor invoices (purchase order based invoice verifiction) and facing currently some major challanges of a business requirements to interface alternative "payment remit to" addresses of vendor invoices. Our current setting consider the data exchange via iDocs into our SAP system, but unfortunately we are unable to process any deviating "remit to" address in the incoming document. As an ARIBA private ID we indicated the combination of "company code" with "vendor number". Can anybody advise how other companies resolved this challange? Thanks for your input, Jakob Kistler

Hi,
I am sending only answers.If wrong pls correct me.
1.A,C
2.C
3.A,B,D,E
4.ACE
5.ABCD
6.B
7.BE
8.ALL
9.ABC
10.ABCDE
11.A
12.ABCD
13.E
14.BC
15.ALL
16.ABC
17.ACD
18.AC
19.B
20.ACDE
21.DE
22.B
23.ABCD
24.CD
25.C
26.BDE
27.BCE
28.C
29.CDE
30.BCDE
31.BDE
32.A
33.B
34.ALL
35.ABC
36.ALL
37.ABC
38.A
39.ACDE
40.AB
41.ABE
42.CD
43.ABCE
44.CD
45.ACDE
46.BD
47.AC
48.CD
I have sent answers for the questions.If any answer is wrong pls correct me.
Assign points if useful
Regards,
S.VINAYA KUMAR

PassingCustomer Address in IDOC

Similar Messages

Maybe you are looking for