To Transfer LFZA-EMPFK using ALE

Hello,
How can i transfer LFZA-EMPFK using ALE . This segment is not available in CREMAS IDOC Type.
Thanks in Advance..
Regards,
Hazam

Hello Hazam,
I have the same problem. How you did to fix this issue?
Thank you in advance

Similar Messages

How to transfer tabl content using ALE

Hi All
I need to to transfer the content of a HR table (T526) using an ALE scenario. However I have not found a way to do this. I stumpled over CONDA2 but not quite sure if this suits the bill. Anybody out there who can help.
I am not an HR wiz so bear with me if this is dead obvious.
Hope somebody can help
Cheers

Hello Bowie,
Could you please help in how to use CONDA2 message type in ditributing HR Configuration data like data from following tables..
T001P     Personnel Area/Subarea
T500P     Personnel Areas
T503     Employee Group/Subgroup
T511     Wage Types
T512T     Wage Type Texts
T512Z     Permissibility of Wage Types per Infotype
T528B     Positions
T554S     Attendance and Absence Types
T554T     Attendance and Absence Texts
Thaks,
Venkat

Data transfer using ALE/IDOC into XML.

Dear All,
I have to transfer FI document data (FB01) from the sap system ,convert it into XML and dump it in 1 of the file servers.I want to do this using ALE/IDOC.Is it possible to do the same and how.Similarly i want to do the same for Vendor and Customer master i.e sending the data in XML format.
Kindly Suggest how do i go about doin the same..Its very urgent.Please help.
Thanks & Regards,
Lailu Philip.

In continuation:
Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
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.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
Hope this will help you,
If you want me to explain more, you can give me your email id.
Reward with points incase you are satisfied.
Regards,
Sushama

Transfer Order using ALE

Hi,
What is the program/transaction for sending Transfer Order(Message Type WMTORD) using ALE.
What is the program/transaction for sending Transfer Order Confirmation(Message Type WMTOCO) using ALE.
What is the program/transaction for sending Transfer Order Cancellation(Message Type WMCATO) using ALE.

Hi Sundar,
For this you need to configure the warehouses in OMKY T-code. And your Functional consultants can assign the output type for the transfer orders then they will transmit thru ALE.
Regards,
Raghav

How to transfer the transactional dat a using ale

hi to all abap gurus
i heard that we can transfer the transactional data ( like so data , po data ) using message control technique by ale technology . . can u please give all steps in message control technique with one exapmle . i searched in the forum but i did not get answer . pls points will be rewrared for good answers. if u want to give links pls give exact links .

Hi ,
here is the configuration.
MESSAGE CONTROL (USING EDI / ALE)
For Purchase order (Message control using EDI and message type ORDERS) STEPS
Settings to be done in the Sending system
From NACE
Choose Application EF ( Purchase order), press on condition record
Output type NEU Purchase order / double click ;choose Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11) execute. Key in the data (vendor vendor11, name name1, partner function - VN, Partner Vendor11,Medium 6 (EDI), time 4(send immediately), language EN).
Press on output types , choose NEU Purchase order, double click, Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time send immediately, Transmission medium EDI, Partner function VN)
Create RFC destination from SM59 (ZNARA_ALE_EDI).
Create a port from ZNARA_ALE.
Create partner profile vendor11 under LI and not LS. PARTNER NUMBER SHOULD BE SAME AS THAT OF VENDOR SET IN THE CONDITION TYPE.
In the outbond parameters of the partner profile Vendor11 key in the data (Reciever port -> ZNARA_ALE,
Basic type ORDERS05, Message type ORDERS ) Go to the message control and key in the data (Application EF, Message type NEU, Process code ME10, Transfer immediately )
Create a purchase order from ME21 with data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11). System will generate an outbond Idoc automatically which can be seen from WE02.
For Purchase order (Message control using ALE and Message type ORDERS) - STEPS
To transfer the idoc from Client 555 to 500
Settings do be done in 555.
From NACE
Choose Application EF Purchase order, press on condition record
Output type NEU Purchase order / double click ;choose Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11) execute. Key in the data (vendor vendor11, name name1, partner function - VN, Partner Vendor11,Medium A (ALE), time 4(send immediately), language EN).
Press on output types , choose NEU Purchase order, double click, Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time send immediately, Transmission medium ALE, Partner function VN)
From SALE create two logical systems and assign them to the respective clients (ZALERECV_N 500, ZALESEND_N 555).
From SM59 create RFC destination with the same name as that of the receiving logical system (ZALERECV_N).
From BD 64(distribution model), create a model view with Technical name ZNARA_PO (message type ORDERS, Sender ZALESEND_N, Receiver ZALERECV_N). Generate partner profiles. Distribute.
Note that partner profile will be generated under LS.
Settings do be done in 500.
From NACE create two logical systems and assign them to the respective clients (ZALERECV_N 500, ZALESEND_N 555).
From BD 64(distribution model), keep the cursor on Technical name ZNARA_PO. Generate partner profiles. Note that partner profile will be generated under LS. Change the process code to ORDE in the inbond parameters .
Now in client 555, Create a purchase order from ME21 with data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11). System will generate an outbond Idoc automatically which can be seen from WE02. The purchase order details will be updated in 555 thru the inbond idoc.
IMP data for message control in Sales order creation.
Partner profile to be created under KU.
Outbond parameters in the partner profile (Message type ORDRSP, Basic type ORDERS02, partner profile - SP) In Message control (Application V1, Message type BA00, Process code SD10)
Notes:
Check the entries in the NAST table to see whether outbond idoc has been created successfully or not
If you have choosen collect idocs in the partner profile, use trans code BD87 to process them
Table EDP13 - Partner Profile: Outbound (technical parameters)
Table EDP21 - Partner Profile: Inbond (technical parameters)
Please reward if useful.

Transfer history notifications from one system to another using ale/inotif

Hi experts,i wan't to transfer 15000 completed,historical notifications from one sap system top another.
I use ale configuration to do this.
I have set rfc connections,message type,distribution model and i've generated partner profiles.
My question is how can i create thenotification idoc?
In MM with message type matmas using transaction code bd10 we send materials creating idoc.In my case for notifications i read that i can do this using transaction code inot.But i am doing this and a mesage:notification rejected appears.
I then try to distribute the model and a rejection message appears with
Reason: Distribution model is currently being processed .
Can you suggest something??
I've read tha i might will need to create badi..

Hi Dear,
its possible only with the help of ECM , you need to do some work around too.
ECM should be extended to include the classification. In fact, the EXACT SAME change number should be used. In PLM, it's important that all of the changes related to a material become active in a cohesive unit. We can talk about those details if you need some background.
Unfortunately, in the split-client scenario, you're toast on any hope of using the same ECM number, due to the internally defined number range. The best you can do is create a new, externally assigned number range in the production client, and generate the number internally in the staging client. You can then make the change in the staging client and ALE it over to the productive client.
The next nasty part is going to be retroactive changes. You can't simply back-date a change. You have to change every occurrence of a dependency, class, characteristic, etc, that has existed in production as of that back date. So, the smartest practice is to never allow any back-dated changes. Require orders to be cancelled and re-created with the new effective date.
Check and revert back.
Regards
Ritesh

Procedure for transfer data between clients using ALE

Hi all ,
I am new to this concept .
I want to transfer the material master data from quality client (200) to Development Client(100) using ALE and IDOC, how to do ?
What would be the procedure ? plz let them explain step by step of definition along with screenshot / process ....
Regards
Deepa.

T.Code: BD54
Step 1:create a logical system qaout in quality system
Step 2:create a logical system devin in quality system
Step 3:create a logical system qaout in development system
Step 4:create a logical system devin in development system
T.Code: SCC4
Step 5:Assign qaout to 200 client in quality system
Step 6:Assign qaout to 100 client in development system
T.Code: SM59
Step 7: Create R/3 type (or ABAP type in ECC)RFC destination RFCDEV in quality system
T.Code: WE21
Step 8: create Port with above rfc reference in quality system
T.Code:BD64
Step 9:Create distribution Model (use matmas message type) in quality system
then Environment ->Generate Partner profiles
Then Edit ->modelview -> distribute
T.Code: BD10
Step 10: select the material for distribution in Quality System.

Routings and Work Centers Transfer using ALE

Can anbody has written inbound function modules
for Routing and Workcenters using message types
LOIROU and LOIWCS using ALE Transaction POIM
High points will be rewarded.

Hi,
Check the FM for routing
IDOC_INPUT_ROUTING_CREATE .
Regards,
Sharath

Issue in Data transfers using ALE for E-Recruiting standalone system

Dear Experts,
We have an issue in data transfers using ALE. We are having standalone system where E-Recruiting is maintaind seperately and the version is EHP5.
When we configured iDoc in Sandbox and its working fine. But when it comes to Dev and Quality servers this is not working fine.
we have created iDocs using the following filters.
For Object P: Infotypes 0000, 0001, 0002, 0003, 0006, 0024, 0105.
For Objects O,S: 1032, Subtype: 0010
For Object: 1001, Subtype: A003, A008, A012, B007
For Object O: 1001, Subtype: A002, B002, B003, B012, Tyoe of related object: O,S
For Objects: C, O, S, Subtype: 1000, 1002, 1028
For Object:C, Subtype: 1001, Subtype: A007
When we do the data transfers in Sandbox using PFAL it is transferring the data properly.
But when we do the same iin Dev and Quality servers we are not able to do it and gettign 52, 51 errors.
Here we are facing a strange issue. For some Users when we transfer data it is transferring data but with 52 error messgae.
For some users I am getting 51 error where i could not transfer any data.
For some users, when we tranfer O, S, and P related data is moving but getting mostly 52 error and all the relationships are not moving here for O,S and properly. But P related CP, BP and NA are getting created successfully.
It is happening only in Dev and Quality server and that too some users are able to get transferred but not all.
Where will be the issue? How can we resolve this?
Any help will be appreciable.
Thank you in advance.

Hi Sekhar,
Have a look over these threads.
Errors in ALE data transfer to E-Recruiting.
http://scn.sap.com/thread/1535402
BR,
RAM.

Using ale u can send from sap to sap and sap to non sap systems

hi,
using ale u can send from sap to sap and sap to non sap systems,
then what is diff b/w ALE and EDI

Hello KALYAN KUMAR,
Application Link Enabling (ALE)
1.You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems.
2.ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
3.ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
1.You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor).
2. The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12).
3. This enables communication with non-SAP systems.
By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message
I hope u understands the difference:)

Creating Sales Order using ALE/RFC

Hi Friends
I required to do data transfer process in my implementation using ALE/IDOC. Since this is my first step in ALE/IDOC, I need help from an expert to start on.
1st scenario is using ALE in same client & same sap system.
2nd scenario is using ALE in diff sap system / diff client
3rd scenario is using ALE in legacy to sap system.
the data to be transferred:
a) from Purchase order to Sales order
b) from RFQ in one client to RFQ to another client.
Please provide me your valuable help on configuring ALE & RFC on this. since this is standard project, i would like to use maximum standard object on developing the above requirements.
Jagan

Hi Basha,
Do you need to display the header items and detailed items?
If the BAPI Contains Output values in R/3 side.
I mean to say if BAPI contains 4 line items.u can get thru wdjava the followinf way.
1. Create webdynpro application.
2.Import the model.
3.Create Customcontroller and model binding .
4. Write the execute method in controller.
BAPI b = new BAPI();
WdContext.node<BAPI>.bind(b);
give inputs for BAPI
b.setname(" ");
b.setno("");
wdContext.currentBAPI().modelObejet().execute();
wdContext.node<output>.invalidate(); in try catch
5. create view or when u give the dynpro application its
in the add custom to view and drag BAPI custom to view .
6.Crete UI for ur table thru insertTemplate table directly mapp the output values.
7. deploy and run
U can get the out line items .
Or any thing else post ur requirement.
Thanks
Lohi

Explain the situation for using ale , bapi ,session ,call transation, di

what is the use of bdcmsgcall,
if any erroe occur in the legacy records how to rectify it?
In what situation we can go for lsmw.
Kindly explain the situation's for using ale , bapi ,session ,call transation, direct input.

Hi ashok,
chk this.
the functionality of both idoc and bapi are same.
the main difference in BAPI is it is used for Third party application like JAVA, VB etc.
and IDOC is used transfer data from the SAP to sap or non-sap system.
For details refer the contents below
ALE
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.
ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.
ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.
The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.
ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.
BAPI
BAPIs provide a stable, standardized method for third-party applications and components to integrate into the Business Framework. These interfaces are being specified as part of SAP's initiative with customers, partners and leading standards organizations. Also, SAP has implemented the emerging Object Application Group (OAG) specifications with BAPIs.
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Session method is to populate the data by filling BDC structure
and keep as session to process from SM37 to post in appropriate Transaction.
Call transaction method is to post the data directly into the Transaction from an Executable program.
Session method SAP defined Function modules.
U can see more help on the differences in the SAP help.
hope u got an idea.
rgds
anver
<i>if hlped pls mark points</i>

HR Master Data using ALE

Hi Guys,
Can you tell me how to pass all HR Master Data using ALE and IDOC to one system to another (outbound transaction). This will automatically generate outbound Idocs every time an applicable reference data record is created and/or changed in SAP HR system. I dont have any experience using ALE your help will be appreciated. Points will be given
Thanks.

Hi,
The program to transfer HR Master Data it is RHALEINI transaction PFAL, this program run in HR system to send information with message type HRMD_A.
Yoy need
Distribution model (BD64),
RFC Destination (SM59 )
Partner profiles (WE20)
Logical system (SM30) V_TBDLS
I hope this help you.

Issue in transporting changed material type using ALE-IDOC

Hi All,
I am sending the material master data from one system to another using ALE-IDOC.The issue is that teh material type is not getting sent from one system to another after changing the material type.I mean the changes in material type are not getting updated.I will be indeed thankful if anyone can guide me resolve this issue.
Thanks.

Hi,
Not all the fields that are changed in material master are sent in the Idoc. Material type is one such field.
Create change pointer on some other field ex. net value or material desc. and transfer the material type changes under it.
KR Jaideep,

How to send inforecord conditions using ALE (message type COND_A)?

Hi,
I have sent Purchasing Inforecords through ALE using t-code ME18.
Now, I would like to know how to transfer the conditions through ALE (message type is COND_A).
Thanks a lot,
Kaveri

Hi,
Please go through this thread.
[Pricing Condition Records initial upload - COND_A]

To Transfer LFZA-EMPFK using ALE

Similar Messages

Maybe you are looking for