Enhanced Infotype (IT0002) field in HRMD_A07 IDoc

Hi All,
I have enhanced SAP standard infotype 0002 (via PM01) to include one new field(NWFLD1). The infotype functions perfectly well with the new field(NWFLD1).
I would now like to see this new field in the IDoc that is generated via change pointers. At present the IDoc (HRMD_A07) does not reflect the new field.
[I guess I'd need to incorporate this new field in an IDoc segment and then assign this new segment in the Tech. attributes for IT0002 and maybe also use some BADI/UserExit to transfer the values].
What steps do I need to take to achieve this?
Many Thanks in Advance.
Sanjay
PS: I have no problems with custom infotypes which work almost 'out of the box' when I create a new IDoc Segment and specify that as the 1st IDoc segment in the Tech. attributes for the custom IDoc via PM01.

Hello Sanjay,
I have a similar issue as of yours.
I had to add 2 custom fields to the standard IT0002.
I have created a new segment and attached to the extension and maitained the same in T777D.
But as of now no data is getting populated for that new segment.
I guess I also have to do some develoment but not sure where and how?
Thanks in advance for the answer.
Naveen.

Similar Messages

HRMD_A07 Idoc to update InfoType 0014 does not delimit existing PA0014 rec

In ECC 6.0, we are using HRMD_A07 Idoc to update infotype 0014 using update data received from a third party application. In XI, I am creating the Idoc with Update Code "U" with E1PLOGI, E1PITYP and E1P0014 segments. E1P0014 holds the data for the latest record.
If I directly pass the Idoc thru ALE layer, It creates records for the new date range on E1P0014 segment, but does not delimit the previous record by changing its end date. This results in two records in PA0014 with end date of 12/31/9999 - which is wrong.
I also tried using a wrapper FM to create additional segments in the Idoc representing the existing record in PA0014, with the end date being delimited to incoming record's beg. date minus 1.
This also results in just creating two additional records in PA0014 corresponding to the two segments in Idoc while existing record in PA0014 stays intact resulting in two records with end date 12/31/9999.
I also experimented with setting the lock indicator (PA0014-SPRPS) but that also does not result in delimiting the existing record.
Am I missing something? Is there a piece of config that controls this?
Regards,
The time constraint on 0014 is "2"

Hi Jon and Ashish,
I too am facing the same issue that the new IDOC is not delimiting the previous record.
Can you explain how did u get over you issue.
I'm maintaining the same dates in E1PITYP and in E1P0014.
Thanks,
Jilly

Idoc enhancement with new fields and refresh in MII 12.1

Hello all,
I'm using one standard idoc LOIPLO to transfer planned orders from ERP to SAP ME 5.2
I have enhanced this idoc to add some new "custom fields" -> On the ERP side I can see my new fields in the idoc, but when idoc is received in MII, I don't see my new fields (it's still the "old" idoc version). In 5.1, I remember that we had to stop/start the message listener in MII and new fields were available, but in 5.2 it does not work.
-> Message listener is now configured at Netweaver level and we stop/start it, but the new fields are not in.
Any idea how to "refresh" the idoc version in MII ?
Thanks and regards,
Michaël.

Restart the NW server
Restarting the Java process should be enough...
Perhaps also via the "cache refresh" tool normally used for Webdynpro stuffs...

HRMD_A07 Idoc to MDM using PI

Hi Team,
We had a scenario where the HR Idoc (HRMD_A07) data is getting integrated to MDM 7.1 using PI 7.1
For example 1 Pernr is having Multiple status like Active, InActive , retire etc.., so we are getting Infotype 000 & 001 multiple times.
So how do we need to Map to target where target has only 1 structure.
Source Structure
<EPLOGI>
<E1P1TYP>
      <IT0000>
            <PERNR>
            <BEGDA>
            <ENDDA>
      </IT0000>
      <IT0001>
            <PERNR>
            <BEGDA>
            <ENDDA>
            <BUKRS>
            <PERSG>
      </IT0001>
      <IT0002>
            <PERNR>
            <BEGDA>
            <ENDDA>
            <ENAME>
            <ANRED>
      </IT002>
     <IT1000> </IT1000>
</EPLOGI>
Target Structure to MDM
<Record>
<EmpNo>
<Status>
<Last_Name>
<First_Name>
</Record>
Here when we execute 2 perner's (10004300, 10004435) IDOC is getting created we are getting source structure as follows
<EPLOGI>
<E1P1TYP>
      <IT0000>
            <PERNR>10004435</PERNR>
            <BEGDA>
            <ENDDA>
            <STAT2>3</STAT2>
           </IT0000>
      <IT0001>
            <PERNR>10004435</PERNR>
            <BEGDA>
            <ENDDA>
            <BUKRS>1030</BUKRS>
            <PERSG>10</PERSG>
      </IT0001>
      <IT0002>
            <PERNR>
            <BEGDA>
            <ENDDA>
            <ENAME>xxx</ENAME>
            <ANRED>1</ANRED>
      </IT002>
     <IT1000> </IT1000>
</EPLOGI>
<EPLOGI>
<E1P1TYP>
      <IT0000>
            <PERNR>10004300</PERNR>
            <BEGDA>
            <ENDDA>
            <STAT2>2</STAT2>
           </IT0000>
           <IT0000>
            <PERNR>10004300 </PERNR>
            <BEGDA>
            <ENDDA>
            <STAT2>3</STAT2>
           </IT0000>
      <IT0001>
            <PERNR>10004300 </PERNR>
            <BEGDA>
            <ENDDA>
            <BUKRS>1030</BUKRS>
            <PERSG>10</PERSG>
      </IT0001>
      <IT0001>
            <PERNR>10004300 </PERNR>
            <BEGDA>
            <ENDDA>
            <BUKRS>1030</BUKRS>
            <PERSG>12</PERSG>
      </IT0001>
      <IT0002>
            <PERNR>
            <BEGDA>
            <ENDDA>
            <ENAME>yyy</ENAME>
            <ANRED>2</ANRED>
      </IT002>
     <IT1000> </IT1000>
</EPLOGI>
The Output target Structure should be as follows...
<Record>
<EmpNo>10004435</EmpNo>
<Status>3</Status>
<Last_Name>xxx</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>2</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
I had done an message Mapping as follows.
IT0001 ==> Record
PERNR ==> Empno
STAT2 ==> Status
ENAME ==> Last_Name
As per the mapping I m getting Output Structure as follows
<Record>
<EmpNo>10004435</EmpNo>
<Status>3</Status>
<Last_Name>xxx</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>2</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
<Last_Name>
<First_Name>
</Record>
There are some values missing in target for the Record <EmpNo>10004300</EmpNo> since the Infotype IT0002 is not repeated. Some Infotypes are not getting repeated, so the values are not getting mapped to target like Last_Name, First_Name etc...
but how do we solve it by using message mapping, Can we use any Java UDF or XSLT Mapping for this issue.
the problem in brief is some infotypes in source is getting multiple times and some are getting only 1 time.
Please suggest.
Thanks in Advance,
Sriram

Hi Raj,
The Mapping is working fine for a single Employee details, In the above target you can see the output correct for
<Empno>10004435</Empno>
If an Employee has multiple status then we are getting multiple Values of same infotype(Segments) like 2 IT000 & IT001, but for some infotype in the same IDOC we are not getting Infotype IT002, so for that record we are not getting the values in output.
For Example if an Employee has only Active status then that Employee will have only 1 action so he will only have 1 IT000,IT001 etc.. then for that record we will get the output correct.
For this Input
<EPLOGI>
<E1P1TYP>
<IT0000>
<PERNR>10004435</PERNR>
<BEGDA>
<ENDDA>
<STAT2>3</STAT2>
</IT0000>
<IT0001>
<PERNR>10004435</PERNR>
<BEGDA>
<ENDDA>
<BUKRS>1030</BUKRS>
<PERSG>10</PERSG>
</IT0001>
<IT0002>
<PERNR>
<BEGDA>
<ENDDA>
<ENAME>xxx</ENAME>
<ANRED>1</ANRED>
</IT002>
<IT1000> </IT1000>
</EPLOGI>
The Output is as follows which is correct.
<Record>
<EmpNo>10004435</EmpNo>
<Status>3</Status>
<Last_Name>xxx</Last_Name>
<First_Name>
</Record>
If an Employee has status Active and Withdrawn status then he will have 2 actions and so he will have 2 IT000, IT001 segments. For this Example see the input structure
<EPLOGI>
<E1P1TYP>
<IT0000>
<PERNR>10004300</PERNR>
<BEGDA>
<ENDDA>
<STAT2>2</STAT2>
</IT0000>
<IT0000>
<PERNR>10004300 </PERNR>
<BEGDA>
<ENDDA>
<STAT2>3</STAT2>
</IT0000>
<IT0001>
<PERNR>10004300 </PERNR>
<BEGDA>
<ENDDA>
<BUKRS>1030</BUKRS>
<PERSG>10</PERSG>
</IT0001>
<IT0001>
<PERNR>10004300 </PERNR>
<BEGDA>
<ENDDA>
<BUKRS>1030</BUKRS>
<PERSG>12</PERSG>
</IT0001>
<IT0002>
<PERNR>
<BEGDA>
<ENDDA>
<ENAME>yyy</ENAME>
<ANRED>2</ANRED>
</IT002>
<IT1000> </IT1000>
</EPLOGI>
See the Output of this above input
<Record>
<EmpNo>10004300</EmpNo>
<Status>2</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
</Last_Name>
</First_Name>
</Record>
The First Segments are getting mapped correctly to Output. but the second segments are only not getting mapped since some values in Infotype or segment IT002 are missing, Means the Output till this record is correct
<Record>
<EmpNo>10004300</EmpNo>
<Status>2</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
But the second record for the same employee is missing.
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
</Last_Name>
</First_Name>
</Record>
in the above output we are missing </Last_Name>,</First_Name> etc where according to business it should be
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
as per business we need to use the previous IT002 data of the same employee in previous action.
How can we get the previous action details in message mapping.
Thanks in Advance,
Sriram

Enhance infotype 2003

I want to enhance infotype 2003.
I'm going through PPCI transaction, i've created structure CI_2003 with a new field.
I've created modulpool ZP200300, and i've inserted a new entry in table T582C.
But when i check the infotype via PA30 my new field is not shown,
Any ideas???

Unfortunately you cannot enhance the Time Infotypes.. pl take a look at this
Re: Add new field to 2001 infotype

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

Way to modify the employee's information (enhanced InfoType) in MSS?

In MSS General Information/ Related Activity area, the manager can modify the employee's information (Addr. Family Member, etc.), as it is a standard module.
Now we have an enhanced InfoType in ECC backend, and want to make it can be modified by the manager through MSS like the other information(Addr. Family Member, etc.).
Is there a way to realize this?
Thanks very much.
ps. We don't have the NWDI environment. EP 7.0 SP10.
Weiming

General notes
1. You really should have error checking after most lines
2. You don't need to get the field ids every time.
Something is wrong in your implementation or description. Or both.
You are attempting to get an object from the array. Then you modify the data in it. Then you set it back into the array.
You don't create a new object anywhere.
So which is it? Is the array empty or is it populated with objects and you are just setting the data in each? The code suggests both (obviously illogical.)

How can i send Comments field data through IDOC HRMD_A06-E1P0035?

Dear all,
We need to post the legacy system data for infotype IT0035 using IDOC - HRMD_A06-E1P0035 to the SAP R/3 system.In this segment (E1P0035) there no field for the 'comments' to send the data. Pls let us know, is there any way to pass data through E1P0035 segment for the 'comments' field of IT0035?
Thanks in advance.
Ram Rayapudi

Hi Ram,
Comment fields in infotypes are not stored in the infotype-tables itself, but in PCL1-Cluster TX.
In Standard-SAP there is no way to pass this via ALE. Even the infotype-table-field ITXEX, which say that there is any textfield present, is clear in ALE.
If you really need to transfer this data, you have to do ALE-amplifications.
Regards,
Herbert

Enhancing infotype 0222

Hi all,
I am trying to enhance infotype 0222 by adding a custom field using tcode PM01.
Field is added in pa0222 table but when I go to pa30 and tried to create record for 0222 the additional field is not being showed.Any setting is required for this infotype?
Can anyone help me regarding this.
Thanks in advance.

you need to assign your enhancement to the main module pool in table T582C
Mosule Pool Screen Program Screen
MP022200 2000 ZP022200 0200
once you have done this you should be able to see your enhancement.
Regards
Jules
Edited by: Jules on Jul 29, 2008 12:56 PM

Cannot enhance Infotype 2007

When I am trying to enhance Infotype 2007 for adding two fields, it says infotype cannot be enhanced.
I enter the infotype 2007 in single screen tab of PM01transaction and click on Generate objects, but it gives a error message saying infotype cannot be enhanced.
Please let me know how this infotype cannot be enhanced.
Any pointers will be awarded.

Do you have autharization to do that?
Please check with other infotyp to make sure do you doing Right
Best Regards

Enhance Infotype (P1704) Student additional data

Hi
Iam trying to enhance the infotype P1704. After enhancing that, those fields should be visible in Student master data(PIQSTD).
Can any one help me how can I do that.
Thanks and Regards
Meshack Appikatla.

Infotype and piqstd program is totally different program so you have to copy original program in the piqstd and change to include all the fields you added in the infotype.
regards,
jin dal

Enhance infotype 0077 screen number 2008

Hi,
I want to enhance infotype 0077 screen number 2008.
Using PM01, i created enhance single screen record with infotype 0077 with version 08.
But the additional field appear on screen number 2000 instead of screen number 2008.
How to add the additional field to 2008 instead?
Thanks.
Best regards,
Xiang Li Heah

Hi Volker Binder,
Try "Infotype Screen Control" in T588M.
T588M is a table and there is no column name called "Infotype Screen Control", can you provide further infomation on this?
Hi Sheetal,
My requirement is to add sexual orientation field into IT 77.
The added field need to be display/edit on PA30 (screen number 2008).
Using PM01, i created single screen enhancement on IT 77 with version 08 (GB).
Using PA30, by selecting different employee, the additional fields display on screen number 2000 but it is not display on screen number 2000.
Many thanks.
Best regards,
Xiang Li Heah

Enhancing an already enhanced Infotype

Hi Experts ,
Can you provide me the steps to enhance an already enhanced infotype . I need to add two more fields but when I add through PM01 , it is refreshing the already enhanced fields

Don't generate the objects. Since the infotype is already enhanced, you just need to edit the CI_PNNNN structure and add the fields next to the ones already there and also change the screen ZPNNNN00 0200 to include those new fields.

Enhance Infotypes for P.A. and O.M.

How to enhance Infotypes for P.A. and O.M.
Please help me.
Thanks in advance.
vamsi.

Hi VAmsi,
Use PM01 Trns to enhance..
<a href="http://www.sapdevelopment.co.uk/hr/hr_infotypes2.htm">Infotype enhancement- Step by step</a>
Rgds,
Jothi.P
*reward if useful.

Enhancement of a field in R/3 to BW

Hi All
I have an enhancement issue.
Data flow is as follows. (R/3)ZTABLE-(BW)ODS-IC
that means data is coming from r/3 ztable into bw ods and hence the cube.
Now the R/3 consultant had enhanced a new field in the ZTABLE.
What i have to do is, by replicating the datasource, the field is to be
enhanced in ODS, ODS update rules, and hence update data in the DATA target
which is cube. How would i do this.
i have modified the ODS with the field of r/3, now how do i move data from
ods to ic.ODS had successfully got updated with the new field of R/3. How to
update in IC
Plz help
assign points to all.
Regards

Hi,
Is it full load or delta? if it is a full load select "Update ODS data into Data targets" from the context menu of ODS. If it is a delta load again it depends on your requirement whether you want to update the historical data to that particular char or not.
hope it helps..
regards,
raju

Enhanced Infotype (IT0002) field in HRMD_A07 IDoc

Similar Messages

Maybe you are looking for