Retrive a field from an Idoc

Hi eveybody
I´ve got the next scenario:
JDBC---->PI-(Idoc)----->SAP
SAP -(Aleaud)--->PI--
>JDBC.
How could I retrive a field from reference Idoc when the Aleaud Idoc is processed??
Im going to try to explain it better.
In the Outbound Idoc travel a field called FIELD_A.
Before the Aleaud Idoc is sent to PI I need to retrive this FIELD_A that travelled in the reference Idoc and send this FIELD_A in the Aleaud Idoc because I need it in the query used in the JDBC adapter.
How can I do this????
Thanks everybody.
Regards

Hi,
Refer to this link..it will help you.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8e7daa90-0201-0010-9499-cd347ffbbf72
Regards,
Gaurav Jindal

Similar Messages

Retriving single field from two tables which are unrelated

Hi experts..
i would like to retrieve a field say X from two database tables TAB1 and TAB2 which are unrelated . Can you give me a way to retrive the field X from TAB1 and TAB2 in a single select statement on perticular condition.
Reward points if aswered..

Hi,
If the field is in two tables,you can use for all entries. But anyway two select statemetns are needed.
If you want single select statement, try using subquery.

How should i remove the filed of e1p0041 segment field from generated idoc

Hi Experts ,
       I have a requirement , whenever an idoc is generated for the particular segment(e1p0041 ) all the fields of infotype should be
in generated segment , but there is no need of some field like dat01, dat02, in e1p0041 segment .
     but it is only do programmatically .
    Please give an help .
thanks in advance.
Venkat

Hello Raju
Thank you for your reply.
Unfortunattely the Field tab doesn't have the Appearance in it.
The field tab contain only the following Items:
Type : Image Field
Caption:
URL
Embed Image Data
Sizing: Scale Image Proportionally
Presence: Visible
Locale: Default locale
There is no item named "Appearance".
I am using AdobeLiveCycle Designer 8.0
Version 8.01.3250.1.491864
Regards
dstj

Modify field from idocs segment

Hi
I am new with Idocs and i have to change 2 fields from a segment in my idoc.Is this possible.If yes,how can they be modified?
Also i tried to place a break-point in my FM that generates the idoc but the debugger does not stop in my FM,eventhough the idoc is generated with succes.Help please.
Thanks

Hi,
Creating Custom IDoc type and Message type
All the objects created should be present on both source as well as target system(s).
1. Create segments - Transaction WE31
Create a segment ZRZSEG1
Add all fields of table ZCUSTOMERS to it
Save the segment
Release it using the menu path Edit -> Set Release
Similarly create two more segments given below
Seg. ZRZSEG2 - to hold all fields of table ZSOHEADERS
Seg. ZRZSEG3 - to hold all fields of table ZSOITEMS
2. Create Basic IDoc type - Transaction WE30
Create a Basic type ZRZORDER
Add the created segments in the hierarchy shown
Maintain attributes for each of the segments
Save the object and go back
Release the object using the menu path Edit -> Set Release
3. Create/Assign Message type - Transactions WE81/WE82
Go to WE81
Create a new Message type ZRZSO_MT
Save the object
Go to WE82 and create new entry
Assign the message type ZRZSO_MT to the basic type ZRZORDER
Also specify the Release Version
Save the object
Thus we have defined the IDoc structure which will hold the data to be transferred.
Please Refer Following Link of IDOCS,
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE+IDOCS
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
For Debugging IDOC.
Execute transaction WE19 , in Existing Idoc give the Idoc number and Execute it will take you to another screen. In this press the Inbound Function Module tab , Give the Function Module and check the check box Call in Debugging Mode , and process In ForeGround.
Thanks & Regards,
ShreeMohan
Thanks & Regards,
\ShreeMohan

Extraction of unloading point field from R/3 to SUS via IDOC ORDERS05

I am extracting unloading point field from R/3 to SUS via ORDERS05.
R/3 filed is EKKN - ABLAD
IDOC Field is E1EDKA1 - ABLAD
But E1EDKA1 is partner function dependent, as it has different values for different partner functions like E1EDKA1 AG, E1EDKA1 LF, E1EDKA1 WE.
While EKKN - ABLAD is not partner dependent.
Please guide as to how to map these two fields.
Regards,
Parag
9881240969.

Hello, partner functions are :
AG : Requester
LF: Vendor
WE: Delivery address
field ABLAD is for the unloading point so it should be mapped on E1EDKA1 with partner function WE.
Regards, Luciano.

Remove field from IDOC

We r sending customer master IDOC from one system to other. We do not require a field to be sent. Can someone suggest is there any way to remove or hide that field. We are using standard IDOC type DEBMAS06.
Thanks,
Aparna

hi,
you can not delete the field but there is option to delete the segemnt.
if you do not want to send the segement with out that afield data ,clear the field data by reading segment in the user-exit
and send.
The below steps are mentioned in the belwo link..
[Steps to delete segemnt...from an idoc|https://wiki.sdn.sap.com/wiki/display/HOME/StepbyStepprocedureforcreationof+IDOC]
3.2 IDoc reduction
3.2.1 Principle
Standard basic IDoc types are often adapted to all imaginable interfaces. However, it sometimes happens that the sent volume is too big compared with the needs. A filter can applied (see above), which represents a dynamical method.
The number of segments or the number of fields in a segment can also be reduced in a static way, while still keeping the structure of the basic IDoc type. Indeed, for all basic IDocs, SAP had envisaged their reduction.
A reduced IDoc has less segments than the basic IDoc, provided that the deleted segments are not mandatory. The segments of a reduced IDoc can also have less fields than the corresponding segments of the basic IDoc.
Dealing with the standard basic IDoc types, their integration function module already takes into account the possibility of a reduction. The advantage to use reduced IDocs seems to be obvious then: to profit from standard functions while reducing the volume of exchanged data.
3.2.2 Customizing
Launch the BD53 transaction (IDoc Reduction Maintenance: Initial Screen).
In the Reduced message type field, type the value ZVISTAPM_REDUCED, then press the Create button.
In the popup window which appears, type in the Message type reference field the value MATMAS.
Validate. In the next popup window, type a short description for the new reduced message type. Validate.
In the following window, select the segments and the fields needed for the new reduced message type.
Save.
Prabhudas
Edited by: Prabhu Das on Jul 6, 2009 11:46 PM

Upload fields from SAP R/3 to BW

Dear All,
I'm looking for a method to upload fields from SAP R/3 to BI 7.0.
My testing case as following:
- Upload table DFKKKO \ field OBEL from R/3 to BW
- I created a Generic Datasource and select this field.
- When coming back to BI, I replicate the metadata from SAP source system and can display my Generic Datasource.
- I create the Info Package for this Generic Datasource but when I run the scheduling, I didn't find any data in PSA table.
So this is my questions:
- Is this method (generic datasource) suitable for uploading from SAP R/3 to BI or there is anything else better?
- Why the data cannot uploaded to PSA table? (I got this error message from Monitor "EDI: Partner profile inbound not available" and "Some IDocs have error status" but don't know how to correct)
If there is any possible response, I shall give reward point.
Many thanks,

Hi
I think you have missed the mapping part in BW....did you create the transformation in BW side before loading the date?You have to map the R/3 field to BW infoobject.

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

Replication of bp name field from ERP to CRM

Hi experts,
We have a problem in ERP to CRM master data replication.
We have already connected our ERP (ECC 5.0) system to CRM 7.0.
We have made initial master business partners (bp) data load from ERP to CRM without problems.
All bp fields, including NAME (but000-name_org1) are transfered correct from ERP (KNA1-NAME1) to CRM.
We have a z program in ERP that is used by users to change the customers names (KNA1-name1).
When we use our custom program in ERP to change the kna1-name1 field in ERP, the bp name field is not changes in CRM.
Using XD02 or FD02 in ERP to change the name (kna1-name1) field in ERP the replication of this field to CRM is correct.
KNA1 table is updated correctly in ERP using our custom program .
What does transactions XD02 and FD02 has that make name filed replicated in CRM?
Thanks in advanced.

Hi,
First variant:
You have to retry load business partners by request:
Tcode R3AR4, R3AR2, R3AR3
So, system retrive new data from tables and transfer to CRM.
Second variant:
You have to add to your z-program part, there you fill data in the CRM system also (via RFC).
Denis.

How to change field mapping in IDOC

Hi Experts,
My requirement is to create a purchase requisition automatically through an interface using the IDOC sent by a *source client*.
For this i have used PREQCR as the message type, PREQCR02 as basic type.
E1BPEBANC & E1BPEBANTX are the segment type i have to use.
I have created a Z process code in which the function module that i have used is IDOC_INPUT_PREQCR.
With the help of this i can map all the field values to PR.
Now there is a field in this idoc called vendor which comes from the source client.
Now the value that is maintained in this field(vendor) should go to the Text Id that is maintained at the header level. ( i.e. the header text. i.e. In transaction ME51N, the text IDs which we can see at header level, the vendor value should go in one of this text Id ).
Now how do i do this, because I am using standard funciton module IDOC_INPUT_PREQCR in which there is already field mapping that this vaue should go in this field and so on...
Do I have to use an exit for the same ?? If yes then which is the exit ??
Please suggest.
Regards,
Priti.

Hi,
I think there is no userexits available during the processing using function module "IDOC_INPUT_PREQCR". You have to copy this function module to a Z function module. Change as per your requirement and attach the new function module with the Z Process code created by you.
Regards
Vinod

Problem in retriving workitem id from uwl in abap webdynpro

Hello,
Curently, I've a problem similar with this post : Problem in retriving workitem id from uwl in abap webdynpro
But unfortunatelly there is no answer :/
I've followed this tutorial : http://wiki.sdn.sap.com/wiki/display/WDABAP/IntegratingWebDynproABAPapplicationswithUWLforworkflowin+Portal
And I have a problem in my WD Abap. The WI_ID field is empty (initial).
Here is my XML :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'
>
<UWLConfiguration version="1.0">
     <ItemTypes>
          <ItemType name="uwl.task.webflow.TS90000087.ED1CLNT100" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
            <ItemTypeCriteria systemId="ED1CLNT100" externalType="TS90000087" connector="WebFlowConnector"/>
            <Actions>
               <Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproABAPLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
                 <Properties>
                    <Property name="WebDynproApplication" value="zps_pnpi"/>
                    <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
                    <Property name="DynamicParameter" value="WI_ID1=${item.externalId}"/>
                    <Property name="openInNewWindow" value="yes"/>
                    <Property name="WebDynproNamespace" value="sap"/>
                    <Property name="System" value="ED1CLNT100"/>
                    <Property name="display_order_priority" value="5"/>
                 </Properties>
                 <Descriptions default=""/>
               </Action>
            </Actions>
          </ItemType>
     </ItemTypes>
</UWLConfiguration>
Here are the parameter defined in my application :
WI_ID     000000000000     SWW_WIID
WI_ID1     ${item.externalId}     STRING
And, i've made the test with both the WI_ID and the WI_ID1 in the XML but everytime, no value at all.
Could you please help me ? It's been three days I'm looking for a solution to get my Workitem ID in my Webdynpro ...

In fact, it's quite strange, I added the menu and toolbar display and I can see that my url contains the data ...
http://<begin_of_the_url>DynamicParameter=System%3DED1CLNT100%26wi_id%3D000000629442%26WI_ID%3D000000629442%26WI_ID1%3D000000629442<end_of_the_url>
So ... how is it possible ?
And the next question, how can I get the full url so I can parse it myself ?

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

Need billing text field name for IDoc mapping

Hi Friends,
our users use CRM web application to send orders to SAP via IDocs. They want to have billing text (In German it is called Rechnungstext or Faktura text) so that they can enter some text here if they want to enter something. My question is, what is the field name and IDoc segment for billing text? We need this information to map in XI.
Br, Sats.

The solution is:
The standard Idoc text segment can be used for the text in sales order. From SD side the text types have to be customized. This is necessary for the XI mapping.
Regards,
Sats.

Retriving of data from different tables

retriving of data from different tables depening of the primary key this key field is there in all tables if it is there in one v table it should continue to other tables otherwise it should get exit from that it should display information message or otherwise success message if it is there in all tables .

Im writing the concept, just check it.
SELECT * from kna1 into lt_kna1.
if sy-subrc eq 0.
selest * from lfa1 into lt_lfa1
for all entries in lt_kna1.
endif.

Populate partner number from return IDOC.

Hi Experts,
I have a requirement where I need to populate partner number from return IDOC to the delivery document. The partner number will not be necessarily have a master data in SAP.Example: I will get a forwarding agent number which will not have a master data created in R/3, but still SAP should allow me to save the delivery with the number that I put in the delivery header-partners with appropriate partner funtion defined by us. Ideally my IDOC will carry any number which I need to populate under header partners in the delivery with out getting any error message saying "No master record exists for XXXXXX". Please provide your expert opinion.
Regards,
Emaya

Emaya,
You cannot save a Partner Function with a Partner Number that doesn't already exist in SAP. Therefore you either need to have the partner(s) created in SAP, or find somewhere else to store the data. There are a few free-format fields in LIKP that may suit your purpose, alternatively you could extend the iDoc & table LIKP to incorporate a new field.LIKP-LIFEX is a good candidate if you're not using it already, or of course there's always a text field.
Cheers, Paul.

Retrive a field from an Idoc

Similar Messages

Maybe you are looking for