New field in MATMAS Idoc

I would like to add new field from MARD which was not included in standard MATMAS. There are some MARD fields in MATMAS already and I like to add one more field. Can someone give me step by step procedure in brief please ?. Thank you

WE30 - create segment
WE31 - extend you idoc and add your created segment to it.

Similar Messages

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

Can we add new field in standard idoc segment ?

HI all,
My requirement is to add new field in segment named E1EDL44 (Idoc named - DELVRY03).
Please guide me how to proceed.
thanks
manish

Hi Manish,
You cann't add any new fields into any of the standard segments like E1EDL44 segment.
Inorder to achieve this you need to do the following:-
Create a new segment and with the new fields and this new segment should be added as a child segment to the E1EDL44 segment. You need to write a piece of code to populate that new segment in the userexit. You should create a extension for your basic type DELVRY03. This way you can achieve this scenario.
Thanks,
Mahesh.

ADD FIELD TO MATMAS IDOC

Hi all
I need to add a field (LABST) in to the STANDARD MATMAS IDOC structure.
How can I Do it?
Can someone help me please.
Thankyou

Hi Simon,
You have to extend the IDoc.
Transaction code is WE30. Please check these sites to get more info.
http://help.sap.com/saphelp_470/helpdata/EN/dc/6b7d6243d711d1893e0000e8323c4f/content.htm
http://sap.ittoolbox.com/documents/document.asp?i=2358
Kindly reward points for helpful replies.
Thanks
Vinod

Have to populate new field in pexr2001 idoc type (out going payment order)

Hi All
I want to populate extra field( internal sap generated invoice number) in the PEXR2001 IDOC TYPE.But I dont know which user exits i have to use. program we are using wasRFFOEDI1
was it
EXIT_SAPLIEDP_901
EXIT_SAPLIEDP_902
EXIT_SAPLIEDP_903
or
Do I have like i have to use user exit <b>EXIT_SAPLIEDP_002</b>
I could nt find where it is called in the program RFFOEDI1. Could you help me where to find this.

Hi,
It is quite deep ... but please check this.
1. Go to SE37 and enter FM FI_EDI_PAYEXT_PEXR2001_OUT.
2. Double click on FORM FILL_IDOC_PAYEXT (include program LIEDPF2F).
3. Double click on FORM HEADER_PAYEXT (include program LIEDPF28).
4. Double click on any FORM FILL_SEGMENT_*. (i.e FILL_SEGMENT_IDKU1).
5. Then double click on FORM STORE_PEXR_SEGMENT (include program LIEDPF15).
6. In here, you should be able to link to FM EXIT_SAPLIEDP_002 using CALL CUSTOMER-FUNCTION '002'.
Regards,
Ferry Lianto

Adding new field in extended idoc type

Hi,
I need to add one field in the basic type. Already an extension is created for this basic type. So i think I can not modify the basic type.
I am looking pointers for this solution. Should I change the already created extension or should I create a new extension?
Thanks
Rajneesh

You should create a new extension .
Modifying the existing extension can cause undesired effects to the already setup message types and partners .

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...

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.

IDOC - add new field in in existing segment definition

Hi,
For segement type say Z1MARA1 if we need to add a new field in segement definition say Z2MARA1 SAP is not allowing to add new field if we tried to cancelled the realsed 30E it not allowing since the SAP realease which we are working is 640 so only we can create new segement defination with version Z2MARA1001 with new field added but issues is that the partner Profile for outbound parameters the Segment release in IDOc Type is 31I so if we change this segment release in IDOC type to new version ie., 640 then it will pick all the new segement associated with it due to which the the format in which we pass the segements to third party will change so is there any way to use the existing segment definition which is release 30E & add addition field to it. Only one way I found is that when i try to cancel the released message is trigger so in the debug if I make it success it allows to add new field in existing segment definition but which is wrong way of doing is there any way we can used same segment definition & add new field without adding new version & new released.
Thanks in advance.
Rajeev

Varma,
I know that we can add new segement with new version my question is existing segement definition can we add a new filed because in partner profile we specified release 31i so even we create new segement type then version will be 640 so it will not pick the latest version.
Thanks
Rajeev

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.

IDOC Segment Adding a new field

Hi all!
My disclaimer: I know less than nothing about IDOCs. So hopefully I lead you down the right path. I have searched SDN and then tried google. As far as I can tell I've gone thru the right steps. But since it isn't working I must have skipped a step.
Here's what I've done:
1. Changed the segment via WE31. I had to cancel the activation. So I activated it again. It did generate a change request.
2. Updated the custom function module. Hard coded a value into that field just to see if it would work.
Tested it by running the invoice transaction. I see the IDOC with all the fields except for the one I added.
Next:
1. Cancel the activation on WE31.
2. Cancel the activation for the Object via WE30.
3. Activate the segment via WE31.
4. Activate the object via WE30.
5. Verify the structure was correct via SE11.
All looked good, I tested again. Again the IDOC was generated with all the fields except for the one I added.
I've since tried some other things. That do not really make a lot of sense, but I tried them. Does anyone know what I'm missing? How do I get the new field to display on my IDOC?
(I've also checked the partner profile via WE20 and verified the message type and object...)
Thank you!
Michelle

1. you have to activate WE30/WE31
2. you have to maintain your IDoc & extension in the WE20 outbound parameters.
3. you have to create a CMOD Project to activate your customer Exit for Incoice IDocs
4. you have to fill the new z-field with relevant value in the Function Module "assigned in CMOD".
if all steps are done. Put a breakpoint in the module to see that the z-field is filled.
Regards,
Gordon

Creating new material using i/b MATMAS IDOC

Hi mates,
I'm trying to create a material in R/3 using an inbound MATMAS IDOC. The material type I use is confiugured for internal number assignment. So, I'm leaving the E1MARAM-MATNR blank.
But, the IDOC failing saying 'No Material Transfered'.
I'm using '005' for the field MSGFN in E1MARAM, E1MAKTM, E1MARMM etc. Is this the right value?
I'm trying to create a material with only the basic view data maintained.
Whats wrong/missing in my config?
I appreciate ur inputs.
thx in adv
praveen

Hi Praveen,
Use WE19 transaction to execute the function module IDOC_INPUT_MATMAS01.
Use different values for the MSGFN field and check it
Regards
Arun

MATMAS idoc with classification details - reg

Hi,
I am working in a project related to the transfer of Material Master from one system to another ( Both are R/3 systems).
I am currently using the message type MATMAS with basic type MATMAS05. With the above message type i am able to generate an idoc from source system with all of the details except for the classification details.
For classification i have configured the message type CLFMAS and CHRMAS, in the CLFMAS i am able to successfully generate an idoc with BD91/BD92 tcodes. But when the idoc is generated, the idoc gives the list of charactersistics managed in the class at each segment level but not able to retrieve the values maintained by me during the material master creation. In order the target values for each of the characteristics in the class is empty.
Please clarify me with the following queries:-
a) Is that really required to push both CLFMAS and CHRMAS for a material master classification related field values ?
b) How to get the characteristics values maintained in the material master at the idoc level ?
c) How to link the CLFMAS generated idoc and the MATMAS idoc to link the relationship?
Thanks for the understanding.
Thanks and Regards,

Classification of a material has to be send with CLFMAS IDOC separate from the material.
Usually you first distribute all characteristics and classes, then the materials, finally the classification.
You have to enter the new material number in segment E1OCLFM field OBJEK of your classification Idoc.

Adding field in standard IDOC Segment E1EDL24

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

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

Error while adding a new field to the Segment in we31

Hi ,
I am getting error when i am trying to add the new field to the cust. segment.
It is released for the adding the new fields i am cancelling the release , but i got a message like this
Error while resetting release of segment 'segment name'.
it is comming from the message class EA and message number 259.
Thanks in advance.
Reagrds,
bharani

Hi,
Have you tried Cancelling the release before adding the version?
Select the active version of the IDOC Segment and cancel its release first. Only then you will be able to add a version.
Please let me know if it worked!
Vijay

New field in MATMAS Idoc

Similar Messages

Maybe you are looking for