MES Interface Development (Standard IDOC-MATMAS enriched with Z-Fields)

Hello Everyone,
We have an issue that we want to sent IDOC data to our local MES System. The XML Target Structure of the MES System is given and cannot be changed.
Most of the fields to be sent are in the MATMAS IDOC but some fields need to be enriched with material classification data which are maintained for each material individually in the ERP. To retrieve the data out of ERP we using the u201CBAPI_OBJCL_GETDETAILu201D. Here we perform an iteration about all these fields to read the classification description and the associated characteristic value. Sometimes it can happen that not for each material the value are maintained and then we are getting blank values
Now I coming back to my main questions.
The target structure of the MES XML File is given and need basically just two core segments from MATMAS IDOC.
E1MARAM SEGMENT="1"     -> Key fields needed: Material Number, MEINH, EAN Number etc.
E1MAKTM SEGMENT="1"     -> Key fields needed:: Material Description
The n- Classifcation field need to be listed directly under the segment E1MARM Segment. So the target structure need to be dynamically built with these n Z Field under den Segment with the following structure.
E1MARAM SEGMENT="1"     Material Number, MEINH, EAN Number etc.
1
u2026<ZL161AUSPM SEGMENT="1">
                <ATNAM>MGBEZ_</ATNAM>
                <ATWRT>Galenical Bulk Prod.</ATWRT>
..</ZL161AUSPM>
n
E1MAKTM SEGMENT="1"      Material Description
As stated out above the information from the classification data are filled in an internal table (XML document with several Row)
Questions:
How do I get the information from the internal XML Document into such ZL161AUSPM structure. Shall I rename the rows in the XML Document from Row to <ATMAN>? And how is this possible? I assume that I cannot change the row name in an "MII XML Document"
<?xml version="1.0" encoding="UTF-8"?>
<Rowsets DateCreated="2009-09-04T14:24:58" EndDate="2009-08-31T14:43:13" StartDate="2009-08-31T14:43:13" Version="12.0.6 Build(12)"><Rowset><Columns><Column Description="CHARACT" MaxRange="1" MinRange="0" Name="CHARACT" SQLDataType="1" SourceColumn="CHARACT"/><Column Description="CHARACT_DESCR" MaxRange="1" MinRange="0" Name="CHARACT_DESCR" SQLDataType="1" SourceColumn="CHARACT_DESCR"/><Column Description="VALUE_NEUTRAL" MaxRange="1" MinRange="0" Name="VALUE_NEUTRAL" SQLDataType="1" SourceColumn="VALUE_NEUTRAL"/></Columns><Row><CHARACT>CH0_MES_01</CHARACT><CHARACT_DESCR>CH0_MES_01</CHARACT_DESCR><VALUE_NEUTRAL>AT</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_16</CHARACT><CHARACT_DESCR>CH0_MES_16</CHARACT_DESCR><VALUE_NEUTRAL>AAI-WC</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_01</CHARACT><CHARACT_DESCR>CH0_MES_01</CHARACT_DESCR><VALUE_NEUTRAL>AT</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_05</CHARACT><CHARACT_DESCR>CH0_MES_05</CHARACT_DESCR><VALUE_NEUTRAL>10000.0</VALUE_NEUTRAL></Row></Rowset></Rowsets
How do I get the dynamically the structure under the E1MARAM SEGMENT="1"? with n u2013 integration? This mean if the material has been assigned three characteristic then I need three time the structure under the segment u201CE1MARAMu201D
Is someone experienced with interface development of such Z-Message respectively has someone an idea or guideline to dealt with such issues?
Thanks in advance,
Markus
PGST
PT Business Solution Management- Manufacturing
F. Hoffmann-La Roche Ltd. Switzerland, Basel
Edited by: Markus Schmeckenbecher on Sep 4, 2009 2:33 PM

Markus,
it is a bit difficult to get the structure from your post, but when I get it right you need to add new nodes in a predefined xml structure.
Did you have a look at the Link editor action "Data Item" from the SAP xMII XML Output? You can define a name and value and add it to a given xml structure. A problem might be the target xml if it is not an IlluminatorDocument (which is of kind /Rowsets / Rowset / Row).
If this does not work, you may try to build Local xml structures for all your Z fields, and append those xmls to your target, using the Link Editor Append XML function.
Michael

Similar Messages

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

Development Standards for BW implementation

Hi all,
Any one has any materials on development standards for BW implementation - with any special attention to BI 7.0 implementation?
Thanks for your assistance. Contributions will be rewarded with points.
Regards,
Uche

hi Uche,
check if helps
Multi-Dimensional Modeling with SAP NetWeaver BI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
Modeling the Data Warehouse Layer with BI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3668618d-0c01-0010-1ab5-aa75c3a4dfc2
Frontend Design Guidelines - SAP BI in SAP NetWeaver 2004s
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/58fd9183-0e01-0010-f183-fdc9019f77ab
Enterprise Reporting, Query, and Analysis - Developers Guide
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0901c9bb-0601-0010-49ab-c1770c527673
check
https://www.sdn.sap.com/irj/sdn/developerareas/bi
'key topics'

Need help with interface development

Hi i need help with requirement below with developing interface between or online order system and sap plz lemme know what is bapi i use for creating customer, update and assigining partner id to costumer.
SAP Development
1.     Using standards SAP functional module (with BAPI), create interface that will create/change Ordering party customer in SAP. Following fields are mandatory for customer creation:
     MANDT     Client
     VKORG     Sales organization
     VTWEG     Distribution Channel
     SPART     Division
     KDGRP     Customer Group (= ZORP)
     KUNNR     Customer number
     NAME1     Name 1
     NAME 2     Name 2 (if required)
     SORTL     Search term (short description)
     ZZALTKN     Search term 2 (old customer number)
     LAND1     Country
     ORT01     City
     PSTLZ      Zip Code
     REGIO      Region (state in USA)
     STRAS     Street
     TELF1     Primary telephone number
     TELFX     Primary Fax number
     ZZPRPLANS     Payment Plan
     CCINS     Payment card: Card type
     CCNUM     Payment cards: Card number
     CCDEF     Payment Card: Default Card Indicator
     ZBDGID     Customer Budget ID
     ZHOLD     Budget Hold indicator
     ZZCOSTCENT     Cost Center
2.     Upon successful customer creation system will issues S (success) message that customer has been created.
3.     New ordering party customer created in step ½, will have to be assigned as new partner to its belonging Sold-to/Ship-to customer. Use standard SAP customer functional module in order to perform this partner ID assignment. Partner ID for ordering party should be ZO.
1.7     Enhancement Functionality
Apart from creating a new interface to do the required functionality, the Order Create Interface also has to be changed to accommodate a field to pass the Ordering Party Number on the Order. The technicalities of how we are going to implement the interface will be laid out in the Tech Specs.
Thanks
in advance

You have double posted, please mark this one as "solved on my own" and refer to this thread
need help with interface development
Regards,
Rich Heilman

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.

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

Devloping the Custom IDoc - Integration sceanarios with Peoplesoft

HI All,
We are on mySAP ERP 2005 with SAP HR on the same instance box, PI 7.0 on other instance, and need to integrate for getting the employee data from Peoplesoft into SAP HR.
I suspect that, this requirement can be fullfilled via Custom Idoc. Correct if I am wrong. plz...need ur expertise inputs for the same.
In SAP HR we are having some Infotypes. While developing the custome Idoc, each Infotype should be added as a segment.
We are having the Standard Idoc for SAP HRMS is HRMD_A.HRMD_A06.
In this case how to develop the custom Idoc to include all Infotypes?
Should I write the code to insert the dato from that Idoc to tables.
Please suggest me the procedure.
Regards
Sridhar Goli

And you said they are sening IDOC_XML to you through http, then how it is having namespace, it should be plain Idoc_xml
like
<?xml version="1.0" encoding="UTF-8" ?>
- <ORDERS05>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
Can you explain or give the format to better understand.

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

Material master/Output type IDOC /MATMAS

Hello ,
I want to generate Idoc(MATMAS) whenever a material is created or changed. I could do the same for ME21N/ME22N for PO with PO idoc. Would like to know whether there is output types for material master or anything else so that i can generate Idoc for my senario.
Thanks for ur time.
Jeeva.

Hi,
the configurations which we do for material master is below...we don't give any output for material master,becoz its a master data not transactional data..
        For distributing master data like material master, vendor master, customer master we have standard transaction codes that are provided by sap.
Bd10(send material master)
Bd12(send customer master)
Bd14(send vendor master)
Bd30(boms)
The order of Tcodes are:
           Bd54 (creating logical systems)
           Scc4 (assigning logical systems )
           Sm59 (rfc destination)
           We81 ( message type)
           We30 ( idoc type)
           We31 ( segment type)
           We82 (linking message type and idoc type)
           We21 (creating port)
           We20 (partner profiles)
           Bd64 (Distribution model)
           Bd10 (material master)
Ex: material master.
     Message type: matmas.
     Idoc type: matmas05.
Rewrad if helpful.
Regards,
Nagaraj

FI - Interface triggerring multiple idoc is not getting posted

Hi all,
I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
But the same idoc, when i proccess indivisually get's process gets posted successfully.
I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
As an abaper, I am not able to understand problem to take corrective steps.
Thanks & Regards
shashikant

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

Value mapping, interface mapping, standard funtions and user defined functi

I like have more information abt live scenario's use of value mapping, interface mapping, standard funtions and user defined functions.
How to create user defined funtions and how to use it in XI?
thanks in advance
shiva

Hi,
Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time .The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.
Features
Executing Multiple Mapping Programs for One DirectionBy using an interface mapping you can execute multiple mapping programs consecutively for the transformation of a request or response message. In such cases, an interface mapping comprises multiple steps for which the following applies:
●     The steps are executed in the sequence specified (from top to bottom). The result of the mapping program from the previous step is forwarded to the mapping program of the subsequent step.
●     Each step can reference a mapping program that executes a 1:1, 1:n, n:1, or an m:n transformation. In the case of multi-mappings (1:n, n:1, or m:n), the previous step must create the same number of messages that the subsequent step expects.
●     Multi-mappings use one envelope to put all messages in one structure. If one of the steps references a multi-mapping program, all subsequent steps must use the same envelope.
The mapping for a request message comprises two message mapping programs: one 1:1 transformation and one 1:n transformation. Since the latter message mapping uses the multi-mapping envelope for both the target message and the source message, the message mapping for the 1:1 transformation must also create a transformation result with a multi-mapping envelope.
You do not strictly need to divide up one direction of the whole mapping into different steps. However, this enables all the message formats in one system landscape to be mapped to a central message format, for example. This results in less mapping programs being required because you no longer need to be able to map all the different message formats to each other
Activities
       1.      Create a message mapping on the design maintenance screen of the Integration Builder (see also: Creating an Object).
You can also create multiple interface mappings for the same interface pair.
       2.      Enter the source and target interfaces that require a mapping of the request message, the response message, the fault message, or all three, in the table of the same name. The following restrictions apply:
○     If you want to use the interface mapping in a transformation step in an integration process, you must only specify abstract message interfaces. Furthermore, all objects (integration process, interface mapping, and all objects that reference the interface mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using an input help).
○     If you want to map multiple messages to each other by using a multi-mapping, you can only specify asynchronous interfaces (for further restrictions, see: Multi-Mappings). If any message interfaces are missing, you can also create them by using the function Create New Object ().
If the interface cannot be imported or cannot be created in the Integration Repository (in the case of an external adapter, for example), you must enter the interface names manually. However, it is not possible to check the technical name in this case.
       3.      To import the properties of the interfaces, choose Read Interfaces. The table in the lower area displays tab pages for the request message, response message, and if available, for the fault message, for each mode of the interfaces (either synchronous or asynchronous).
       4.      To develop an external mapping program, export the XSD schema of the respective request or response message as a zip file after you have imported the interfaces. The zip file can contain multiple schema files that reference each other, for example in a multi-mapping. In this case, the schema with the global message element has the name MainSchema.
       5.      To reference a mapping program for the respective message, you have the following options:
○     Select an existing mapping program from the Integration Repository by using the input help (). If this is a message mapping, the default setting of the input help only displays those message mappings that are found using the source and target message in the Integration Repository (in multi-mappings, the first source and target messages are used as the search criteria). However, you can also display any number of message mappings, for example, because you are constructing a mapping from several mapping programs with intermediate instances which have no message types.
○     You can create message mappings directly from the interface mapping. To do this, select the mapping type Message Mapping in the Type column. Position the cursor in the Name column and choose the function Create New Message Mapping () in the Mapping Program frame. The Integration Builder copies the specifications of the messages and their occurrence directly from the interface mapping.
An interface mapping can only reference mapping programs that belong to the same or an underlying software component version of the interface mapping. This ensures that the mapping program can be shipped together with the interface mapping (see: Software Logistics).
       6.      If it is not a mapping for a fault message, you can execute multiple mapping programs in succession for request and response messages:
○     To insert an additional line for a mapping program, choose .
○     To delete the registration for a mapping program, choose .
At runtime, the mapping programs are executed from top to bottom.
       7.      Save the interface mapping.
Regards
Aashish Sinha
PS : reward points if helpful

Standard IDocs for Transfer Order Details

I am integrating SAP WM with an external System. I want to send the Transfer Order details to the external system using Idocs. Please let me know what are the standard IDocs available for Transfer Order and TRM Task.

Hi,
There's no std idoc for TRM tasks to be send to an external system. I am busy developing one for our business process requires TRM tasks to be send down to a voice solution via bapi and then the confirmation thereof back to SAP via idoc.
Regards,
Hein

Projects, is the Standard Functionality the one with COGS created?

Korean Air manufactures AIRCRAFT components and delivers them to customers such as Boeing. It wants to implement ERP (R12) applying Oracle Projects Solution.
Issue
1. When Shipping Type Deliverable is created in Project Module and it is interface to Shipping Execution for Ship Confirm, COGS(Cost of Goods Sold ) for Shipping Item is created and it overlaps with cost of sales per Project/Task.
Question
*1. **When Shipping was done using deliverable of Shipping Type in Project Module, is the Standard Functionality the one with COGS created?*
A. If the number 1 case is Standard Functionality, is there any option to prevent COGS creation?
B. If the answer is no, by what kind of setup is it possible?
C. Does Shipping of Project Module based on “non-asset based warehouse”?
*2. What is the Integration mapping of Project Management, Shipping Execution, Inventory, AR, COGS etc?*
The following are basic process.
1. Quotation-> Contract -> Plan -> Production -> Delivery -> Revenue
A. Using Deliverable in Projects
2. Project: Agreement
3. Task: Unit
4. Purchasing Plan, Production Plan etc. executed based on Project/Task
5. Cost calculation is calculated in Project/Task unit
6. When Task (Tail Number) is completed, deliver to Boeing according to contract
B. Interface through Shipping Execution
C. Ship Confirm
7. Based on cost revenue is recognized according to progression rate.
A. Cost Collect
B. Generate Draft Revenue
8. Based on delivery or contract, account receivable is created and send to customer.
A. Create Event per Task
B. Generate Draft Revenue
C. Interface Draft Revenue to Receivables.

Hello Daniel,
The PCI serial cards are not supported with LabVIEW RT for ETS targets and are not expected to work. We are looking into finding a way to add support for PCI serial devices in RT, but currently that support does not exist.
One possible workaround would be to use a NI ENET-485-X device. The visa resource name will not be COMx in this case. Instead, you will need to enter the long name of ASRL::::::INSTR as documented in the NI-VISA help.
I hope this helps. If you need to speak with your sales representative to resolve this issue, please follow this link. Have a great day.
Regards,
Kristi H
National InstrumentsMessage Edited by Support on 01-18-2005 08:24 AM

Sender Namespace and Sender Interface in the IDOC to IDOC scenario

My question maybe very basic...
It is SAP IDOC to SAP IDOC scenario.
Lets assume that I have done config in XI for:
             Sender = A,
             Interface = B,
             Namespace = C.
My question is:
Is there a place in the source system or somewhere to point that
when an IDOC e.g. DEBMAS is triggered in the source system,
then the Interface should be B and Namespace should be C in the xml file ?
Cheers
Agnie

Hi Agnieszka,
     Check these threads/blogs from you may get some help:
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Idoc-to-idoc scenario
IDoc to IDoc scenario necessary configuration steps
For A-Z help on IDOC, you can refer Michal's book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi IDoc Business Scenarios with SAP XI</a>
Regards,
Subhasha Ranjan

IDOC Posting with new fields in VA01

Hi,
Previously i asked for creating New fields in VA01 screen.
i got that now i need to create a sales order based on the Inbound IDOC which i get and i will be getting new fields which are created .
And this Fields data is coming from an Extension to the Standard IDOC. Sales order is getting created but the new fields are not getting populated nor stored in VBAK Table.
pls let me know why is this.And provide me with a soultion.
MG.

Hi,
i had a similar problem in my last assignment .
I think you are using IDOC_INPUT_ORDERS F/M for Posting the IDOC.
Here once you go into the code at line number 116 you can see that they are calling Transaction VA01 for posting the sales order .
If you go into any perform there you would be having the User Exits . Use the exits and you need to process the IDOC in the Foreground so that you can catch the Screen flow and the screen number , as you do in SHDB.
Now you need to make sure that you are getting the new screens there where you have desigined the fields on the screen.
And write the BDC Code with proper OK Codes before the Save ok code SICH is reached .
And make sure that you are writing the code at the header level only as you need to update the VBAK Table.
As this is a single screen you can directly write the BDC code for populating the fields data and at last make sure that the ok-code you are giving is the right one.
Pls let me know if this problem is solved , i need to check the code in which exit i have written . But here it would be the same EXIt i think .
the exit name is EXIT_SAPLVEDA_002 .
Pls check this and let me know.
Regards,
Naidu.

MES Interface Development (Standard IDOC-MATMAS enriched with Z-Fields)

Similar Messages

Maybe you are looking for