Regarding "WPUFIB01"idoc enhancement

hi ,
i have a std idoc "WPUFIB01" to which i am trying to add two new fields with the use of E1WXX01 cutomised segment.all the process is done using inbound processing.Currently i am using the enhancement name "WPUE0002" and the user exit i am using is "EXIT_SAPLWPUE_130".my problem is that i that i am unable to read the segment "E1WXX01" while processing the idoc.pls help ...thanx in advance..

Hi Rahul,
Did you release the segment and the Custom IDOC TYPE.
Check whether you are using the correct idoc type.
Check if the segment is populated in the idoc.
Regards
Arun

Similar Messages

Regarding ALE-iDoc for Customer Master, J1ID and FD32

Hello all
Scenario:
As per client's requirement we have to develop idoc so that followings requirements will meet:
Say there are two servers a) MDM Server b) PRD Server
1] As and when I'll create customer master data in MDM server then customer master should get created with that data in PRD server
which I can achieve through BD12 by doing some idoc enhancements
2] Simillarly when i'll create data using transaction J1ID and FD32 in MDM Server (Data relevant to customer master) then that data also should get created in PRD server using Idoc
May I know which
1)message type we can use (as we use DEBMAS in case of Customer Master) for J1ID and FD32
2) Any transaction to send data from one server to another server for transaction J1ID and FD32 (as we use BD12 in case of Customer master for sending data created using transaction XD01)
Thanks,
Mahesh

Hello Mahesh,
In the case of customer master it would be better if you would use standard message types and t code to transfer ddata.
But in the case J1ID and FD32 you can build a standalone idoc
Follow these steps to build custom message types and futher transactions
WE81 - Create message type
WE31 - Create segment
WE30 - Create Idoc type
SALE - Define Logical system (not required if already exists)
SM59 - Define RFC (not required if already exists)
WE21 - Define ports (both in sender and receiver)
WE20 - Define Partner profile (both in sender and receiver)
BD46 - Distribue the model view.
SE38 - Create a program to send the idoc in the sender sytem.
SE37 - Build inbound function module to receive the idoc for receiver system
WE57 - Assign FM to message type
BD51 - to change the characteristics for inbound FM
WE42 - Create Inbound process code.
Hope this would help you.
Thanks and Regards,
Ranjith Nambiar

How to find idoc enhancements

Hello Friends,
Could any body please let know how to find idoc enhancements.
for inbound and outbound. Already i had searched in forum.
regards,
phani

HI ,
u can follow the steps:
Transaction: SMOD
Click F4 help for Enhancement
Path: F4help -> SAP Applications -> Logistics general -> Logistics Basic Data ->
Business partners -> Vendor Master.
Find the enhancement as VSV00002, which is an approximate user exit.
Now search for different extensions like VSV00001. Then see for its components.
Identify the appropriate user exit to be u2018EXIT_SAPLVV01_001u2019 (Create Export of
Additional Customer Master Segments). This user exit can be used in outbound ALE
process, meant for filling the data into custom segments.
You have to identify here another user exit as u2018EXIT_SAPLVV02_001u2019, which is
helpful for inbound ALE process. This user exit can be used to read the segments
and post it to Application repository.
Step9: Develop a project to encapsulate enhancements and components.
Transaction: CMOD.
Enhancement: custex and click Create to provide attributes.
Click Enhancement Assignments.
Provide VSV00001, short text and save.
From the initial screen of the transaction, select components and click change.
Find 4 components to be added.
Activate them.
Select user exit EXIT_SAPLVV01_001 for outbound process and double click it. It leads to function builder.
Double click on provided include program ZXVSVU01 and press enter.
Now, write supporting code for IDoc extension, i.e., populating custom segments in IDoc.
Check the code and activate.
Thanks
Shambhu

Regarding ale idocs

Hi....
Please send some FAQ'S regarding ale,idocs
thanks
k..swaminath

Hi,
plz go through the links...
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Reward points if u find useful.
Regards,
Nagaraj

Idocs - Enhancements!

Hi Friends!
    Can any one pls tell what all the enhancements which u ve worked on IDOCS.
    Pls give step by step detail in Creation of segments & FM coding Please.
   Looking for your Help.
   Thanks In Advance.
    Rahul.

Hi Rahul..
These are the Steps for IDOC enhancement.
IDOC EXTENSIONS
SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02.
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.
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 DEBMAS02 does not have a segment or fields that communicate the contact persons 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.
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.
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.
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.
Reward if Helpful

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

PAYEXT IDOC Enhancement for Japan

Hi
We are looking to enhance the PAYEXT IDOC - for Japan. Can anyone tell me the program/function module that is triggered to create PAYEXT IDOC from F110.
Appreciate your help!
Regards

HI,
RFFOEDI1 is the program which creates PAYEXT IDOC you can configure this through FBZP transaction.
Inorder to to execute this program RFFOED11 through F110.
Regards,
Shanmugavel Chandrasekaran

Regarding Outbound IDOC for Goods Receipt with MBGMCR03

Hi Experts,
Please let me know ,how to handle TYPE QUANT fields when i am generating an Outbound IDOC for Goods receipt for message type MBGMCR with the IDOC type MBGMCR03.
At item level when passing the value for quantity received field ,the QUAN value into NUMC or CHAR before MASTER_IDOC_DISTRIBUTE to pass it to data record it is showing correctly in my BADI .
after generating the idoc , the field value is appended with next field value passed.
before generating IDOC
erfmg( 60.000) - ENTRY_QTY(060)
efrme (EA)       - ENTRY-UOM(EA)
after generating IDOC
IN WE02
ENTRY_QTY-060EA
later field values are mismatching .
Please let me know the resolution.
Thanks & regards
Vishnu

Hi,
     Standard Idoc types for invoice is INVOIC01 and INVOIC02.
- Use WE30 for seeing Idoc types with segment.
Or otherwise go for Custom Idoc
           Create Custom Idoc type with required fields,custom output type and assign it to partner profiles.(If there is no std idoc type or output type)
          Use Funtion module MASTER_IDOC_DISTRIBUTE to generate Idocs while saving MIRO, for this you need to find exit or implement implicit enhancement while saving MIRO.
http://wiki.sdn.sap.com/wiki/display/ABAP/StepstocreatecustomIDOC - Creating Custom idocs

Idoc enhancement with ABAP

Hi all,
we are currently in a project to implement SAP HR as HR master and distribute HR master data to other legacy systems using SAP XI.
There will be two different interfaces from SAP HR to XI, one for real-time updates of changes (delta) and one for batch updates of complete records. We use SAP R/3 4.7 ext2 and want to use Idoc type HRMD_A06 which contains all HR data (we will have to add segments for two infotypes, but that is not the problem).
The problem is that there is some information we need to distribute that not automatically gets included in this Idoc type (such as SAP personell number for manager of the org.unit an employee belongs to). My guess is that this has to be filled using some custom ABAP.
Does anyone have any experience with adding such information to an Idoc? We can always find a suitable field in the Idoc to store the values if we only can retrieve the correct information.
And secondly, how do we make sure this extra information is stored for the correct employee segment in the Idoc?
Finally, can we implement this function module so that it runs after the general Idoc is created, runs through the entire IDoc and adds the correct information for each employee segment, and then send the finished IDoc to XI? This goes for both real-time interface (implemented using change-pointers) and batch interface (scheduled job to collect master data).
Any information or experience on this matter will be highly appreciated. Any other suggestions to how this problems can be solved are also welcome.
Thanks in advance.
Best regards, Kenneth Eriksen

Hi Kenneth,
Sorry for the misleading information abt the user exit at the first place.
For batch process,
1. Run PFAL transaction.
2. Follow the same process to determine the manager in user exit EXIT_SAPLRHAL_003. set the parameter flag as 'X'. Also export the parameter 'Flag' to memory id in the user exit after the process.perform the logic to determine manager pernr only if infotype 0001 is filled.
3. Second user exit EXIT_SAPLRHA0_001 will follow the previous exit. Import the parameter from memory id. if flag eq X. no process.
4. Manager pernr will be passed.
For change-pointer process,
only 1001 information should be triggered by change-pointers.
1.)run rbdmidoc to trigger change-pointers for hrmd_a.
2.)user exit EXIT_SAPLRHAL_003 will be executed internally in the first step. should not perform manager logic as no 0001 infotype filled. It means parameter FLAG is blank.
3). in the user exit EXIT_SAPLRHA0_001 , perform manager logic for change-pointers only if flag eq space.
following logic should be followed :
a.) IDOC_DATA fill contains the 1001 records.
b.) loop at idoc_data.
    read each record and determine 0001 infotype for all employees with new manager(as described in my first reply). append the 0001 records into idoc_data_temp.
c.) process each record by record in idoc_data.
d.) after the endloop. move all the records from idoc_data_temp to idoc_data.
now idoc_data will contain only 0001 records no 1001 records.
e.) again loop at idoc_data, perform manager pernr logic.
The change-pointer process is just overriding the standard process and manipulating custom records.
this is the one way of achieving the solution.
The other solution to achieve change-pointers is to perform lot of customization.
1.) create a custom program to read the change-pointers from bdcpv table to read the unprocessed records for message type hrmd_a.
2.)create infotype 0001 records from 1001 data.
3.) also perform manager pernr logic for 0001 records as we are not calling standard transaction(master_idoc_create_smd_hrmd).
4.) follow the logic in the sample program to create idocs.
FUNCTION ZSKIT_CREATE_IDOCS.
""Local interface:
DATA:
*·······control·record·for·the·IDoc
          IDOC_CONTROL LIKE EDIDC,
*·······data·records·for·the·IDoc
          T_IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE,
*·······table·for·the·IDocs·created·by·MASTER_IDOC_CONTROL
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
*·······partner·type·for·logical·system
C_PARTNER LIKE EDIDC-RCVPRT,
*·······help·variable·for·the·check·if·an·IDoc·has·to·be·created
H_CREATE_IDOC.
*·variables·specific·for·this·example
DATA:
*·······field·strings·with·IDoc·segment·structure
E1XITEM LIKE ZSKILL_CAT occurs 0 with header line,
*·······data·to·be·put·to·the·control·record
C_MESSAGE_TYPE LIKE EDIDC-MESTYP VALUE 'XAMPLE',
C_BASE_IDOC_TYPE LIKE EDIDC-IDOCTP VALUE 'XAMPLE01',
*·······segment·types·to·be·put·to·the·data·record·table
C_HEADER_SEGTYP LIKE EDIDD-SEGNAM VALUE 'E1XHEAD',
C_ITEM_SEGTYP LIKE EDIDD-SEGNAM VALUE 'ZSKILL_CAT'.
E1XITEM-SKILL_ID = '12345678'.
E1XITEM-SKILL_TYPE = 'SKI'.
E1XITEM-SHORT_TEXT = 'Test'.
E1XITEM-LONG_TEXT = 'Test skill'.
E1XITEM-TENANT_ID = 'check1234'.
E1XITEM-BEGDA = sy-datum.
E1XITEM-ENDDA = sy-datum.
E1XITEM-SKILL_UP = '01234567'.
E1XITEM-SKILL_DOWN = '3456789'.
append E1XITEM.
clear E1XITEM.
E1XITEM-SKILL_ID = '12345678'.
E1XITEM-SKILL_TYPE = 'Test'.
E1XITEM-SHORT_TEXT = 'Check'.
E1XITEM-LONG_TEXT = 'check skill'.
E1XITEM-TENANT_ID = 'test1234'.
E1XITEM-BEGDA = sy-datum.
E1XITEM-ENDDA = sy-datum.
E1XITEM-SKILL_UP = '01234567'.
E1XITEM-SKILL_DOWN = '3456789'.
append E1XITEM.
clear E1XITEM.
*···put·the·application·item·record·to·the·IDoc·segment
loop at e1xitem.
*···append·record·to·IDoc·data·table
    T_IDOC_DATA-SEGNAM = C_ITEM_SEGTYP.
    T_IDOC_DATA-SDATA = E1XITEM.
    APPEND T_IDOC_DATA.
ENDLOOP.
idoc_control-rcvprt = 'LS'.
IDOC_CONTROL-RCVPRN = 'DI2440'.
IDOC_CONTROL-MESTYP = 'ZSKIT'.
IDOC_CONTROL-IDOCTP = 'ZSKIT'.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
*·in·update·task···"if·application·document·is·posted·in·update·task
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = T_IDOC_DATA.
*exceptions
*···········error_in_idoc_control··········=·1
*···········error_writing_idoc_status······=·2
*···········error_in_idoc_data·············=·3
*···········sending_logical_system_unknown·=·4
*···········others·························=·5.
*·A·commit·work·has·to·be·done.·It·could·also·be·done·in·the·calling
*·application.
COMMIT WORK.
READ TABLE T_COMM_CONTROL INDEX 1.
IF SY-SUBRC <> 0.
*·no·IDoc·was·created,·you·can·react·here,·if·neccessary
ENDIF.
ENDFUNCTION.
5.) also set the change-pointers records as 'processed' status using standard function module.(search for function module starting like change_pointers_read_mode_set)
Please decide between 2 solutions .
Also revert back for any concerns.
Regards,
Senthil

Regarding Exit/IDOC Related TD

Hi,
Can anybody tell me what is the code required to be written folowing TD points.
Before below TD i have populated one internal table in
userexit_save_document exit and submitted following new program need to be written as below:
SUBMIT gv_prog
WITH SELECTION-TABLE t_seltab
VIA JOB gv_jobname NUMBER gv_jobnum "USER puser
AND RETURN TO SAP-SPOOL
SPOOL PARAMETERS gv_params
WITHOUT SPOOL DYNPRO.
As i am new to IDOC Concept can anybody help to write following code!
Create new custom program that will create the CTO deletion idocs to send to WWCLASS
     Requirements:
o     Need to be able to import data in from the save_doc userexit and create and post the idoc
     Import needed data from userexit_save_document
     Fill the control record to send into function (waiting for FA to get this information to me, as they have not yet created the partner)
     DOCTYP =
     OUTMOD = 2
     SERIAL = sy-datum
     SERIAL+8 = sy-uzeit
     IDOCTP = ORDERS05
     MESTYP = ORDERS
     MESCOD = ??????
     RCVPRT = ??????
     RCVPRN = ??????
     RCVPFC = ??????
     RCVPOR = ??????
     Fill the E1EDK01 segment (Header level segment)
     CURCY = currency
     ZTERM = zterm
     BELNR = order number (vbeln)
     Fill the E1EDP01 segment (Item level segment)
     POSEX = item number (posnr)
     ACTION = 001
     Fill the E1EDP19 segment (Item Object Identification segment)
     QUALF = OID to represent old GCTO id
     IDTNR = GCTO ID from vbap
     Generate the idoc
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL                  = cntrl data
    TABLES
      COMMUNICATION_IDOC_CONTROL           = cntrl data(returned)
      MASTER_IDOC_DATA                     = idoc data
   EXCEPTIONS
     ERROR_IN_IDOC_CONTROL                = 1
     ERROR_WRITING_IDOC_STATUS            = 2
     ERROR_IN_IDOC_DATA                   = 3
     SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
     OTHERS                               = 5
     Based on the documentation for this standard function, you will need to do a commit work after calling the program in order to ensure the idoc is dispatched.
o     Need to be able to capture failures and send report to users in e-mail
     Failures fall into 2 categories:
     An IDOC was created, but the posting fails with error status. In this case, we still want to capture this in the file as a failure, but the users should re-process this with standard SAP transactions (can find status of created idoc in the returned communication_idoc_control table).
     An IDOC was NOT created for some reason. In this case, we will need to capture all the necessary information needed to try and re-create an idoc
     File should be sent via e-mail to users defined in a table.
     Use standard FM SO_NEW_DOCUMENT_SEND_API1 to send document to specified users
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
       EXPORTING
            document_data              =
            document_type              = 'RAW'
            put_in_outbox              = ''
       TABLES
            object_content             =
            receivers                  =
       EXCEPTIONS
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            OTHERS                     = 8.
     Document Data should include the email header information. Something that denotes to user that this is an WWCLASS CTO Deletion IDOC Error Report
     Object Content should include the following information:
o     IDOC# (in cases where the idoc was created, but has fail status)
o     Order Number
o     Currency
o     Terms of Payment
o     Item Number
o     GCTO ID
     Receivers should be the list of addresses that will receive the email.
o     Read table ZCMAIL with REPID = this program name, and MAIL_LIST = to retrieve all the addresses that will need to have the report sent. Will need to send the FA the name of this program so they can setup the table entries properly.
o     Need to add parameters to program that will also allow the user to run this program manually so they can re-create the idoc in cases where the idoc was erroneously not created in normal process.
     Allow user to enter a file name that could be uploaded from their hard drive that will contain all data need to create the idoc.
     Generate the idoc based on data in file.
     File could look similar to the data reported in the error report
Can anybody help me in writing code for above TD!
Thanks in advance.
Thanks & Regards,
Deep.

HI,
Any solutions for the same!
Thnaks,
Deep.

Idoc enhancement

hi all
i have to enhance debmas idoc can anybody tell me procedure for doing that.

Hi,
refer following link:
http://help.sap.com/saphelp_nw70/helpdata/en/dc/6b82a343d711d1893e0000e8323c4f/frameset.htm
Bhavish

Regarding Inbound Idoc creation

Hi,
I am trying to create a Idoc from a xml file without using XI.
I can read the details from the file and populate a internal table.
I am not clear when the IDoc number will be generated.
Can any one gtel me which FM actually starts the inbound proces?
Which FM will generate the IDOC no for the incoming Idoc ?
I am not clear as to which function module i should pass my internal table with data to create a IDoc.
Please help
Regards,
Vignesh

Hi,
try MASTER_IDOC_DISTRIBUTE function module for create idoc.
rgds
shibu

Regarding Custom IDOC Creation

Hi All,
I Am New to ABAP , Any one Please Give me the Step -By Step Procedure to create Custom IDOC.
I Have this Link with me.
Step by step custom IDOC creation
But I Don't Know that What should i Give field names and Data elements
How to create Field names And Data elements
Regards
Vamsi

Hi,
U need a custom IDOC when the elements in the standard IDOC is not there according to requirement. ex. in IDOC cremas04 u want the Country code should be there.
Then U go for custom iDOC and create a Y/Z i.e custom idoc and add one structure and add the required fiellds.
Check this link for Step by Step guide
http://www.erpgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
CHeck this link for a IDOC ...The steps are mentioned in details about creating custom idoc..
http://www.allsaplinks.com/idocbasicsunderstanding.html
http://www.allsaplinks.com/idoc.html
http://www.allsaplinks.com/idoc_sample.html
Please check this link.
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Regards

Regarding OM Infotype Enhancement

Hi Friends,
I got a requirement to enhance a OM Infotype HRP5122 and HRP5126.
Please give me a hint to do the enhancement.
Thanks,
Anil.G

Hi,
Enhanement for hrp5122.
open the infotype , and the last field is include and its dataelement. With that include you can make the enhancement.
Regards,
Vani.

Need information regarding ALE-IDOC

I am new to ale-idoc, any body can please send me ale-idoc scenarios and examples.
Regards

Hi,
Please refer to the details mentioned in the hyper-links beow.
You will get the details how to go about it.
To see the IDOC & status check it in WE02/WE05
You will get step by step process.
ABAP Development
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
http://help.sap.com/saphelp_45b/helpdata/en/35/b0ea5187a62488e10000009b38f9b7/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/c4/6bc368fef411d28d0900104b56737d/frameset.htm
ABAP Development
Follow below steps to create custom IDOC.
1.Create segments through transaction WE31.
2.Create IDoc Type through transaction WE30 by attaching created segments.
3.Message type through transaction WE81.
4.Link Idoc and message type in WE82 transaction.
Check the transaction WEDI for ALE settings
Check these links for more details on IDoc's:
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
Hope this will help.
Regards,
Priyanka.

Regarding "WPUFIB01"idoc enhancement

Similar Messages

Maybe you are looking for