Standard Idocs.

Hi All ,
I'm Venkat . Can anybody tell me ,Is any standard Idocs are there for Sales Order, Purchase Order like for example MATMAS for materials master like that.
I'm waiting 4 reply.

Hi Venkat,
SALESORDER_CONFIRMDELIVERY(Message type) -> message type for Delivery Confirmation (SalesOrder)
Idoc types are:
SALESORDER_CONFIRMDELIVERY01
SALESORDER_CREATEFROMDAT201
SALESORDER_CREATEFROMDAT202
SALESORDER_CREATEFROMDAT2 -> Sales order: Create Sales Order
Idoc types are:
SALESORDER_CREATEFROMDAT201
SALESORDER_CREATEFROMDAT202
SAORDERTEST -> SALES ORDER
PURCHG -> Order Confirmation/Change
PURCONTRACT_CHANGE -> BAPI to Change a Purchase Contract
Idoc types are:
PURCONTRACT_CHANGE01
PURCONTRACT_CREATE -> BAPI to Create a Purchase Contract
Idoc types are:
PURCONTRACT_CREATE01
PURCONTRACT_GETDETAIL -> BAPI to Display Details of a Purchase Contract
Idoc types are:
PURCONTRACT_GETDETAIL01
PURSAG_CHANGE -> Change a Scheduling Agreement
Idoc types are:
PURSAG_CHANGE01
PURSAG_CREATE -> Create a Scheduling Agreement
Idoc types are:
PURSAG_CREATE01
PURSAG_GETDETAIL -> Read Out Details from Scheduling Agreement
Idoc types are:
PURSAG_GETDETAIL01
ORDERS -> Purchase Orders
Idoc types are:
ORDERS01 to ORDERS05 and ORD_ID01.
if you want other details go to WE81 , and u can search all standard Message type.
Regards,
Vijay

Similar Messages

What are the standard IDOC's available in IDES? where can i see in IDES?

Dear All,
Can any body let me know what are the standard IDOC's available in IDES? What is the path for the same?
Thanks in advance for replies
regards
srikanth

Hi,
IDOCs are intermediatery Documents, we can check for IDOCS using Tcode
WE01 : Create IDOC
WE02 : Display IDOC
WE19 : Reprocess IDOC
etc
Thanks
Kalyan

What is the Way of finding all standard IDOC avilable in SAP R/3 modulewise

Dear Experts,
How to know list of all avilable standard IDOCs present in SAP R/3 Modulewise(i.e. HR,MM etc)?is there any standard tcode to see all the standard IDOC(or we have to follow some other way) ?
Eagerly looking for your valuable opinion.
Regards,
Rasmiraj Tripathy

Hi,
I am not sure that it is possible to see module wise.Just go through this we81,we82.
Regards,
Madhu.

Data transfer to sap R/3 with no standard IDoc

Hi all,
I have a situation where i need to transfer data to and fro between SAP R/3 system and an Oracle database.
The data getting transfered is HR data.
For this transfer there is no suitable standard IDOC which can be used.
In this situation what should be our approach?
Pls guide as soon as possible, since its a bit urgent.
Thanks in advance.
Regards
Neetu

Hi Neetu,
If sap WAB AS is >= 6.20 then u can use Abap Proxies(SPROXY) in SAP instead of calling IDOC...
Check this link
D:\helpdata\EN\86\58cd3b11571962e10000000a11402f\content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ab/585f3c482a7331e10000000a114084/content.htm
and weblog..
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Regards,
Sridhar
Message was edited by: sridhar reddy kondam

How to find the Standard Program associated with a Standard IDOC

Hi,
I am going work on enhancing the standard IDOC. Any body can suggest how to find a standard pogram associated with a Standard IDOC. And can any body send some exaple code for extending a standard IDOC and to implement the logic in the standard program .....

Hi,
For outbound IDoc the program can be found:
1) For master IDoc via transaction BD60. Here for the message type you can find the function module used to generate the IDoc. Within this function module you can find the user exit where you can code your logic.
2) For IDocs with message control (output control) we maintain settings for proces code in WE41. This process code will lead to outbound IDoc generation program.
For Inbound IDoc the program can be found:
Via WE42 where inbound process and its related inbound function module is maintained.
In each cases above we can go the function module and find the customer exit where idoc enhancement logic can be coded.
For extending IDoc look at the following links:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm">Extending IDoc - SAP help</a>
It can be summarized as follows:
Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
Hope this helps.
Regards,
Gajendra.

Standard idoc type for Vendor invoices

Hi All,
Can anyone tell me if any standard idoc type for Vendor invoice(Cleared items) exists and if any standard report is there to populate and distribute that idoc?
I want the fields bukrs,belnr,lifnr,bldat,cpudt,zfbdt,zterm,xblnr,waers,dmbtr and mwsts in that standard IDOC.
Thanks in advance

Hi,
check this IDOC types..
SINGLEREMUNRQS_CREATE01 "46A
SINGLEREMUNRQS_CREATE02 "620
regards
vijay

Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
Thanks,
Veeru.

Hi,
IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
Msg: INVOIC
Basic type: INVOIC02
FM: IDOC_INPUT_INVOIC_FI
Process code: INVF
Thanks,
Kumar

Source of xslt mapping and XSD/ XMT target structures for standard Idocs

Hi,
I am working on R/3 - XI - ICH scenario. I need xslt mapping and XSD/ XML target structures for standard IDoc like PROACT01,DELFOR01, DELVRY03. I tried to search it on marketplace but couldn't find it there. As per configuration document, these things are shipped with XI mapping content in live cache CD. But I don't have this CD with me. Can anybody tell me the source for these target structures and mapping program. ( Please share marketplace, site link or send me across the mail [email protected])
Thank you in advance.
Anand More.

Anand the other option is to import the corresponding idocs into your integration repository and then you can view the generated XSD there.
As regards XSLT mapping, you need to basically first identify as to what form you want to transform your source idoc into.
For some help on XSLT mapping check the following threads,
https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/topusers.jspa%3FforumID%3D44
https://www.sdn.sap.com/sdn/collaboration.sdn?node=linkFnode1-6&contenttype=url&content=https://Process Integration (PI) & SOA Middleware
Also have a look at my code samples,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-code-samples/generic xslt mapping in sap xi, part i.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9692eb84-0601-0010-5ca0-923b4fb8674a
cheers
Sameer

How to use BLAREL03 standard iDOC to upload Purchasing contract to SAP

Hello
Guru's
Thanks in advance for your time.
we ae planning to upload purchasing contract details to SAP using BLAREL03 standard idoc.
can any one give me step step procedure to follow.
i am new to IDOC's i need little bit detail. give me with function modules names to upload.
In any way can we test it quickly,by creating text file with mandatory fields on the idoc and upload it.
we just worried about like contract start date,end date,(how it is handling while uploading) the fields which are on tree view of idoc, are not there,if we look at flat file structure of idoc.

Hello
Guru's
Thanks in advance for your time.
we ae planning to upload purchasing contract details to SAP using BLAREL03 standard idoc.
can any one give me step step procedure to follow.
i am new to IDOC's i need little bit detail. give me with function modules names to upload.
In any way can we test it quickly,by creating text file with mandatory fields on the idoc and upload it.
we just worried about like contract start date,end date,(how it is handling while uploading) the fields which are on tree view of idoc, are not there,if we look at flat file structure of idoc.

Adding field in standard IDOC Segment E1EDL24

Hello Friends,
I have an urgent requirement that I have to extend IDOC segment E1EDL24 with two fields PABNR and LFSNR.
When I tries to change the segment in WE31, it shows an error message that you can only modify the segments of customer namespace and cannot modify Standard IDOC Segments.
Can we modify the standard IDOC segments, and if yes, how can we modify the standard IDOC segments. Please clarify.
Points will be rewarded generously.
Regards,
Navin

Hi Naveen,
We cannot Modify the Standard segments. But we have to Create a new Segment and Add these fields.
Then Create an Extended Idoc type
Implement User Exits in Outbound And Inbound ..
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
Reward if Helpful

How to include segments to standard idoc PEXR2002 ..

How to include the below segments to the standard idoc PEXR2002 ..
E2EDK02
E2EDK12
I want to map the check number to E2EDK12-BELNR depending on the document number.
I have a recording in shdb..but my real question is it where to have this logic..
Any suggestion would be highly appreciated.
Thanks,

U will have to create IDoc Extension for this.
Goto WE30 select the Radio button Extension.
Link it with the basic Idoc Type.
Then attach the new segments in the IDoc.

Which option to choose:idoc user exit or copy standard idoc?

Hi gurus,
We are using idoc technolody to implement the interface between R3 and 3rd party system.
Most of idocs are inbound processing, and it seems standard idoc can't meet our all requirements.
So we are considering the option:i choose doc user exit or create new idoc by copying standard idoc.
Which way do you like better?What are the advantages and disadvantages of them?
Any help will be appreciated.
BTW, our customer will upgrade their R3 4.7 system to ECC6.0 after this project the next year.

Hi,
By making changes in the User-Exits, if you can achieve what you are looking for then I would recommend to use user-exits. SAP programs are not bug free and SAP keeps on updating them by releasing hundreds of notes every day. If customer is upgrading to new version in near future then using standard programs are the best option.
Cheers,

Standard IDOC type for Posting Open AR items(Similar to FB01 posting)

Hi,
I need to know if there is any standard IDOC type that can be used to post the incoming open AR items into SAP.
The below are the fields that are coming into the SAP.
Header:
BLDAT     DATS     8     Document Date
BLART     CHAR     2     Document type
BUKRS     CHAR     4     Company Code
BUDAT     DATS     8     Posting Date
WAERS     CUKY     5     Currency Key
XBLNR     CHAR     16     Reference Document Number
BKTXT     CHAR     25     Header Text
Line item data:
BSEG     BSCHL     CHAR     2     Posting Key
BSEG     "KUNNR "Customer Number
or
LIFNR"     CHAR     10     or Vendor Number"
BSEG     WRBTR     CURR     13.2     Amount in document currency
BSEG     ZTERM     CHAR     4     Terms of payment key
BSEG     ZFBDT     DATS     8     Base Line Date
BSEG     ZUONR     CHAR     18     Assignment
BSEG     RSTGR     CHAR     3     Reason Code
Line Item data: tax amounts
BSEG     BSCHL     CHAR     2     Posting Key
BSEG     HKONT     CHAR     10     G/L (Tax) Account Number
BSEG     WRBTR     CURR     13.2     Amount in document currency
BSEG     FWBAS     CURR     13.2     Tax Base Amount
BSEG     MWSKZ     CHAR     2     Tax Code
BSEG     PRCTR     CHAR     10     Profit Center
Thanks
Shiva

Hi
Try
FIDCCP02 or FIDCC*
Regards
Neha

How to Find Out whether Standard IDOC is Availabl for Transaction ?

Hi,
    We are having SAP implementation 4.7E IS-OIL. We would like to know how to find out whether is there any Standard IDOC is Available for the SAP Transaction.
Particularly for IS-Oil related transaction. e.g Load Confiramtion. T-code - O4G1.
    From a Given Transaction code is there any link which can tell whether IDOC is Present or not.
     Kindly help me.
Regards,
Umesh

check for transaction....we41 and we42..
check for proper process code...then check in we57,we81 and we82..
also u can search in google..
UMESH note that u need some fucntional exp for working in IDOC...try to crack yr head ..give time..n u ll get to know the things soon..as there is no defined standards to work in idocs..
for more info u can ask me for [email protected]
best regards
Message was edited by:
        Madan Gopal Sharma

Standard IDocs for Inbound Sales Invoice

Hi All,
Beginner in the forum.
I have a requirement to develop an IDoc interface for Sales Invoice. I am not sure about the Basic IDoc Type, Message Type and Inbound Function Module to be used.
I can see Basic Types INVOIC02/01 and Message Type INVOIC. And the Function Modules IDOC_INPUT_INVOIC_FI and IDOC_INPUT_INVOIC_MM assigned in WE57. As my requirement is in SD perspective, I am little confused which one to use.
Any pointer would be helpful.
Thanks in Advance,
Khanshi

Sales invoices are generated referencing existing orders and deliveries through VF01 or VF04. Most if not all data for creating the invoice comes from the existing order/delivery documents (except may be freight costs etc which are know only during invoice time). So there is no standard IDoc (as most data for creating sales invoice is already there in SAP in the form of reference delivery/order) to create a Sales invoices. Sales invoices created through VF01/VF04 are outbound and can trigger INVOIC message type IDoc through IDOC_OUTPUT_INVOIC which is sent from SAP to the customer for billing purposes.
The IDOC_INPUT_INVOIC_FI and IDOC_INPUT_INVOIC_MM are for creating inbound vendor FI invoice (like that created by FB60) and MM vendor invoice (like that created by MIRO) respectively.
If you want to create a sales invoice through BAPI the below modules are available but I am sure there isn't a standard IDoc function to post a inbound INVOIC IDoc to customer/sales invoice. These BAPIs will of course require you to input the reference document (delivery or order) to create the invoice.
BAPI_BILLINGDOC_CREATE
BAPI_BILLINGDOC_CREATEFROMDATA
BAPI_BILLINGDOC_CREATEMULTIPLE
Best regards,
Vishnu Tallapragada

Standard IDOC/BAPI to create work order in CRM from ECC PS

Hello Guys,
Any input on any standard IDOC/BAPI I could use to create a work order in SAP CRM based on the data feed from SAP ECC (Project systems)?
Any help on this would be really appreciated.

Hii.
Did u get answer of SAP-> XI->CRM. IF so, share wid us.
I m stuck in same kinda scenario

Standard Idocs.

Similar Messages

Maybe you are looking for