ALE: Missing infotype 0002 in Idoc Creation
Dear experts,
I need your help regarding ALE configuration. Currently IT02 is included in the customer distribution model for HRMD_A message type but everytime we create a change in an employee that triggers the change pointer it doesn't capture the changes for IT02. I can only see IT0, IT1, and IT3 but IT02 is also in the filter? do you have any ideas how can I troubleshoot this scenario? thanks in advance!
Regards,
Mike
Dear Krishna,
Hope you are doing good.
I know its very late in getting into this conversation. Since I am also experiencing the same issue, i need some inputs from you.
The error you posted on the top is same what i am getting when I am doing data transfers from SAP HR to E-Rec systems. Our iDoc is working file in Development server but not in Quality server. I am experiencing the same errors what you have mentioned above.
When i checked the error, this error has occurred in subroutine read_namtb for structure of infotype.
Proceedure is to Check the entry for infotype in table T777D (structure, IDoc segment,
expanded structure) and the corresponding structures.
As you have resolved this issue before, can you please suggest what needs to be maintained in the tables such as T777D, T777E, and T777Z.
Appreciate your valuable inputs on this.
Thank you.
Similar Messages
-
ALE - IDOC Infotype 0002 additonnal fields...
hello all
We have add 2 customers fields in the infotype 0002, and we would like to sent the infotype 2 with these
2 new fields.
So we have created an extension which contains a segment with these 2 fields. But unfortunately
with the pfal transaction , these 2 fields are not filled by values.
Has someone have an advice ?
thank youhello all
thx for your contribution
it works well for a specific message that we have updated with an extension which include the segment Z1P0002 , but in our case we have a lot specific message . so we update table Table T777d in order to include specific segment Z1P0002 ( the 3rd after E1P0002, E1Q0002 )
but unfortunately, the fact to update T777d , occurs error for all the message they are not concerning with this extension.
Maybe an another way exists ?
Thx for help by advance. -
Sending the enhanced Infotype 0002 outside SAP via an IDOC
Hello Friends,
We have added couple of Z fields to the standard 0002 Iinfotype table PA0002.
I can see the custom fields in the trans : PA30 screen for infotype 002.
Now, we want to send these custom fields value outside SAP via an IDOC.
Here are the steps I followed :
I created a Z Segment in an extended idoc with the structure PA0002.
I went in transaction PM01 for Infotype 0002 and added the above created Z segment as a 2nd IDOC segment.
In transaction PA30 for 002, I made changes to the custom field value for a person 12039.
Created an idoc via BD21.
IDOC generated with the Z Segment but it doesn't contain any Z custom fields.
Which step am I missing here? Do I have to have a user-exit or BADI to achieve this OR can it be done without writing any code?
Basically I
I will really appreciate your help.
Regards,
Pooja PandeyPooja,
you need to fill each field manually.
check this code i am filling ZHCMS_PI_SEMENT
data: sgmnt_e1pityp type e1pityp.
field-symbols: <wplog> type any.
field-symbols: <wplog1> type any.
data: ixxxx type e1pityp, iyyyy type e1plogi,sgmnt_hcms_pi type zhcms_pi_segment,wa_idoc_data_x type edidd, ls_idoc_data type edidd.
data: lv_p0001 type standard table of p0001 ,lv_p0002 type standard table of p0002 ,lv_p0007 type standard table of p0007 .
data: lv_p0521 type standard table of p0521 ,lv_p0710 type standard table of p0710 ,lv_p2001 type standard table of p2001 .
data: ls_p0001 type p0001,ls_p0002 type p0002,ls_p0007 type p0007 ,ls_p0521 type p0521 ,ls_p0710 type p0710 ,ls_p2001 type p2001 .
data: row_index type sy-tabix,del_index type sy-tabix.
data: lcx_root type ref to cx_root.
fILL THE E1PITYP
try.
Keep the segments which have changed date greater than last run date in update mode
read table idoc_data into wa_idoc_data_x with key segnam = 'E1PITYP'.
assign wa_idoc_data_x-sdata to <wplog> casting type e1pityp.
ixxxx = <wplog>.
loop at idoc_data into wa_idoc_data_x where segnam = 'E1PLOGI'.
row_index = sy-tabix + 1.
assign wa_idoc_data_x-sdata to <wplog1> casting type e1plogi.
iyyyy = <wplog1>.
sgmnt_e1pityp-plvar = ixxxx-plvar.
sgmnt_e1pityp-otype = ixxxx-otype.
sgmnt_e1pityp-objid = iyyyy-objid.
sgmnt_e1pityp-infty = '0001'.
sgmnt_e1pityp-begda = ixxxx-begda.
sgmnt_e1pityp-endda = ixxxx-endda.
clear ls_idoc_data.
ls_idoc_data-segnam = 'E1PITYP'.
ls_idoc_data-sdata = sgmnt_e1pityp.
insert ls_idoc_data into idoc_data index row_index.
APPEND t_idoc_data .
Get the ZZSWISSREID
sort lv_p0001 by begda descending.
read table lv_p0001 into ls_p0001 index 1.
sgmnt_hcms_pi-zzswissreid = ls_p0001-zzswissreid.
Get the custom data from IT0002
sort lv_p0002 by begda descending.
read table lv_p0002 into ls_p0002 index 1.
sgmnt_hcms_pi-zzglobalid = ls_p0002-zzglobalid.
sgmnt_hcms_pi-zzsource_id = ls_p0002-zzsource_id.
sgmnt_hcms_pi-zzlegacy_emp_id = ls_p0002-zzlegacy_emp_id.
ls_idoc_data-segnam = 'ZHCMS_PI_SEGMENT' .
ls_idoc_data-sdata = sgmnt_hcms_pi.
row_index = row_index + 1.
insert ls_idoc_data into idoc_data[] index row_index.
clear : lv_p2001[] , lv_p0001[] , lv_p0002[] , lv_p0710[] ,lv_p0007[], lv_p0521[], ls_p2001 , ls_p0001 , ls_p0002 , ls_p0710 ,ls_p0007, ls_p0521 .
APPEND t_idoc_data.
endloop.
Thanks
Bala Duvvuri -
Hi all,
I am creating one ALE connection.In this connection error is occurs.The error No is 29( Error in ALE service).
1.How to resolve the this error.
2.If any ALE&IDOC creation error occurs,How to resolve.
3. ALE creation single cleint is working or not?
If any cases give examples.ALE Error Messages:
02 - Error passing data to port
04 - Error within control information on EDI subsystem
05 - Error during translation
25 - Processing despite syntax errors (outbound)
29 - Error in ALE service
32 - Resubmit edited intermediate document (DO NOT USE)
Look at this link it has all details of ALE
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1268508,00.html -
Missing of Gender field in infotype 0002
Hi All,
Recently we have upgraded the patch level from 0026 to 0037. The problem is I am unable to see the Gender field(GESCH) in Infotype 0002. I have checked in Std screen of P0002 there also i am unable to find the field. But in the database table the field is available.Previously it was available in infotype 2.
Due to the missing of standard field Gender (GESCH) in Infotype 0002 I am unable to upload the data and also unable to take the std copies of PF form 5 and form 10 where system is automatically taking the Gender column as F(female) instead of M(Male).As per the standard code it checks this field GESCH for "1" and outputs gender as "M" if "1" and "F" otherwise.
Any help in this regard will be highly appreciated.
Regards,
Anjenaya PrasadHi,
Activate the field in the table T588M Q0002-GESCH to standard.
Path: PM->PA->Customizing user interfaces-> Change screen Modifications
Regards
Devi -
Steps for ale idoc creation?
Hi,
I want the complete process of ale idoc generation.
my maild id is [email protected]
Thank You.
From:
Mohammed Moid AhmedHi
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these 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
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Reward points if useful
Regards
Anji -
Encrypt SSN in idoc for infotype 0002
I have to encrypt a field SSN for IT 0002 in idoc.
after transporting i should have ssn in encryptred form.
Is there any function module to encrypt desired field ?
Thanks in advance.Encryption at database level is implemented using the BAdI IDOC_DATA_MAPPER and the enhancement spot IDOC_DATA_CRYPT.
If it only needs to be encrypted for display check transaction WECRYPTDISPLAY. -
IHC errors :valid clearing partner not found and no header details found while idoc creation after f110
Please let me know where the config is missing for ihc automatic payment program.in we02 status is not 53.
Please helpHi
Please share the error message in the IDOC.
If the error message is IHC204 "No valid clearing partner was found", it may be due to the missing correct configuration in Set Up Creation of Payment Requests for Inbound IDoc in FI, which links the clearing partner, ALE logical system partner type and IHC account number.
Cheers
taro -
Missing items in the IDoc for the delivery
Hi to all,
Sorry if not posting in the right forum.
In my customer's scenario, an IDoc is created against a delivery (via the delivery output), and sent via ALE to a distant warehouse system, for picking and GI posting (basic type SHPMNT03).
For some times, the IDoc created against deliveries including BOMs is missing the main item of the BOM (though the BOM main item is in the delivery).
Consequently, the integration in the distant system is failing, because the higher-level item referenced in the BOM sub-items is missing.
Surprisingly, re-triggering the delivery output does re-generate a complete IDoc, where the segment for the main item is back.
I looked almost everywhere, did many searches in OSS (on SHPMNT03, on HIPOS, on E1ELD24 - segment name in the IDoc -, on "Missing items in the IDoc for the delivery", etc...), I even simply googled the web, but I can't even figure out what is the cause for this (I imagined it could be caused by a missing commit in the program generating the IDoc, but don't know whether this make sense).
Any help would be highly appreciated.
Thanks in advance and best regards
Yan
Edited by: Yan Loiseau on Jul 8, 2010 12:52 PM
Edited by: Yan Loiseau on Jul 8, 2010 12:56 PMHello Yan
Jelena is right, you are better off taking it up with SAP. I also did not find any relevant OSS notes.
However the issue, according to my reading, is in the following areas:
1) LV56KF05: INCLUDE LV56KF62 . " FILL_E1EDL24"
This fills the EIEDL24 segment, may be the main item is filled initially and overwritten later.
2) Function Module: IDOC_OUTPUT_DELVRY
You can look at the following OSS notes (though not fully relevant) for some clues:
810981 - Reference data missing in DESADV IDoc from decentralized WMS
537470 - BOM + batch split in decentralized WMS, confirmation fails
752921 - VL563: Higher-level item does not exist
705086 - Higher-level item does not refer to existing item
Hope this helps. Good luck. -
Segment E1IDBW1 is missing for the inbound idoc type PAYEXT
Hello,
the above segment is missing in the inbound idoc - basic type pexr2002.
I have checked in TC-we30 and its available there.
but still the idoc is getting generated without this segment.
can someone suggest.
thanks
ArunHi All,
I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002 and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
We have done the following steps:
- BTE 2441 is available on our release
- house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
- entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
- code maintained in ZXF08U04
The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
Can you advise what we might be missing please?
Thanks and regards
Mike -
IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq
Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===> Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03 Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20 VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20 VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24 POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PMIDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned. -
Change pointers and Idoc creation
Hello,
I would like to create change pointers for any changes regarding one of our customer infotypes: 9002 (hrp9002)
I was able to do that, however, I'm struggeling with the details.
The problem is that I do not want to send any data related to infotype 9002. I just need this change pointer to trigger idoc creation for the related objects.
Example: Let's assume that infotype 9002 gets created for position S 40001234. Once a night a customer report is executed via a job which reads all unprocessed change pointers (including the one mentioned above) and sends the corresponding object. In this case, an Idoc for the holder of position 40001234 should be created WITHOUT data for infotype 9002.
The message type is HRMD_A.
What do I need to do?
Thank you for your input.Hi,
For Info type 9002 we need to implement Badi HRALE00CHANGE_PTRS using below code.
LOOP AT t_changed_objects INTO wa_changed_objects .
CASE wa_changed_objects-infty.
WHEN '9002'.
wa_cp_data-tabname = 'HROBJINFTY'.
wa_changed_objects-plvar = '01' .
wa_cp_data-tabkey = wa_changed_objects .
wa_cp_data-cdchgid = 'U'.
* wa_cp_data-CDOBJCL = 'HRMD_A'.
APPEND wa_cp_data TO t_cp_data1 .
ENDCASE.
ENDLOOP.
IF t_cp_data1 IS NOT INITIAL .
CALL FUNCTION 'CHANGE_POINTERS_CREATE_DIRECT'
EXPORTING
message_type = 'HRMD_A'
TABLES
t_cp_data = t_cp_data1
EXCEPTIONS
number_range_problems = 1
OTHERS = 2.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.
ENDIF.
This code will create entry in BDCP2 table.
After thsi populating segemnet you need to code for below exit as .
EXIT_SAPLRHAL_003
IF PNNNN_NAME = 'P9002' .
*FIELD-SYMBOLS: <FS_plog> TYPE ANY. "Field Symbol for dynamic filling of data based on the structure
*Clearing the SUBRC
CLEAR SUBRC.
* fill workarea for infotype with infotype-data
ASSIGN pnnnn_data TO <FS_plog> CASTING TYPE P9002.
LS_9002 = <FS_plog>.
* move fields
MOVE-CORRESPONDING LS_9002 TO LS_p9002.
* fill IDoc-data with workarea for segmenttype
ASSIGN sdata_data TO <FS_plog> CASTING TYPE Z1P9002.
<FS_plog> = LS_P9002.
CONVERTED = ZCDP_IF_CONSTANTS_DTIRIS=>GC_CROSS .
ENDIF.
It will work fine.
Thanks
Anju -
Goods Confirmation - Idoc creation process???
Hi,
I see that during the goods confirmation process the idocs are created. well i'm aware of the ale configs but my question here is how there idocs are created and which is the process that initiates this...bascially i wish to extend the GR idoc in SRM with added segments but need to know where i got to write the code for the extended segments. this process of idoc created is seen during the call of the work flow WS10400010 but looking into this workflow i cannot see any steps that handle the idoc creation....
nb: my confirmation process happens without an approval step in between.
any thoughts on how to check the process that creates this idoc for confirmation?Duplicate Question from SRM General Forum. It is answered, pls. close the thread. Thanks.
http://forums.sdn.sap.com/thread.jspa?threadID=2134619&tstart=0 -
Custom IDOC Creation from scratch
Dear Experts
This is the first time I am working on an ALE/EDI request from the client from scratch.
This request is for establishing an outbound
data connection to FedEx for the outbound shipping (from FedEx) process. The IDOCs will then be process via a xyz server(our side) and sent to a fedex abcd system. The data connection between xyz and abc has already been established.
The tasks for modifying SAP for the outbound connection are as follows:
1. Create a new IDOC partner for fedex
2. Create new outbound IDOC with trigger points as follows:
Trigger u2013 For plants 1000 & 2000: Upon creation of an outbound delivery coming from a particular storage location, send the new IDOC to the fedex partner for the corresponding order. This IDOC will be used by fedex to determine the receiving party for the materials and creating the appropriate paper work, such as packing slips, customs invoices, etc.
Can some one please tell me the steps required to accomplish this on the configuration side and the development needed (posting program etc)
Theoretically I know the steps of ALV but I am seeking guidance from someone who has done this in real time because I don't know how many of those steps would be necessary for this.
Help would be really appreciated.
Thanks and Regards
Sameer
Edited by: Sameer Ahmed on Feb 29, 2012 8:06 PMHi,
Please check with the below link, there are many step by step tutorials for ALE IDOC creation.
<Link to blocked site removed by moderator>
Edited by: Vinod Kumar on Mar 8, 2012 4:51 PM -
Iam getting any error in infotype 0002 while doing enhancement ...
Dear all
could any one let me know why iam getting this error ,
" TABL HRTIM00WS_PWS_INFTIES was adjusted
Check table HRTIM00WS_PWS_INFTIES (SFCD07/13.06.07/11:34)
Enhancement category for table missing
Enhancement category for include or subtype missing
Field name TIME is reserved (Do not use structure as include in DB table)
Table HRTIM00WS_PWS_INFTIES was checked with warningsif iam doing
enhancement for infotype 0002 ....
i have just added an one custom field ...(zzname , data element is zzname type char 20)as per the business requirement.
regards
vamsiIam getting any error in infotype 0002 while doing enhancement .
" TABL HRTIM00WS_PWS_INFTIES was adjusted
Check table HRTIM00WS_PWS_INFTIES (SFCD07/13.06.07/11:34)
Enhancement category for table missing
Enhancement category for include or subtype missing
Field name TIME is reserved (Do not use structure as include in DB table)
Table HRTIM00WS_PWS_INFTIES was checked with warningsif iam doing
enhancement for infotype 0002 ....
when iam activating .................the structure i got the above error...........please urgent i have just added only one field
Maybe you are looking for
-
Can I drop an IMovie Slideshow with music into IDVD?
Hello, I created (and it took a long time) a slideshow with music using IMovie. Now I want to burn it to a DVD and am realizing I need to put it into IDVD. I saved it to my desktop and then dropped it into the IDVD Magic program but it does not save
-
ASR_PROCESS_EXECUTE - ABAP Webdynpro application keeps looping
Hi, We are implementing HCM Processes and Forms framework and trying to use the standard ABAP Webdynpro application ASR_PROCESS_EXECUTE to be able to Start HR Personnel related processes. Start Processes iview available with the HR Administrator pack
-
How to check a Purchase order sent through EDI?
Dear All , I have created a P.O and in Message tab there is a green indicator which shows that this P.Ois succsfully sent through EDI , also Condition records are well cr
-
Apple push notification service certificate multiple servers
Hello; Can I use one apple ID for more than one Lion server service certificate? Thanks.
-
BPEL 10.1.3.3 - Receiving Mail using MailService.wsdl not working
Hello Gurus, We are having both 10.1.2 BPEL server and 10.1.3.3. In 10.1.2 I could successfully use the mail read method as specified in Sample 117.ReceiveEmails. But when I do the same in 10.1.3.3 I am getting "java.lang.NullPointerException" (while