Doubts on ALE Distribution Configuration

Hi,
Yes , Exactly
And also in XI we need to create the Port, to send the data through XI to the Target application
Regards
Seshagiri

Hi Carsten Heinrich,
Follow these steps:
Step for Configuration fo IDOC in R/3
SM59-rfc destination
IDX1-port
IDX2-load metadata
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Steps to be followed in Creation of Technical and Business System
Technical System
In SLD, click on technical landscape->New Technical System->WebAS ABAP.
Business System.
1.Goto Business Landscape->New Business System->Name the business system.
2. Choose the technical system that needs to be attached->WebAS ABAP->Technical System Name.
Preconfiguration steps for transfer of data to IDOCS
1.Create a RFC Destination in SM59 of XI Server of type.
2.In transaction IDX1 ,create a port for the client of XI server.
3. The port has to be displayed in the idx2 transaction and we should be able to view the idocs which we imported through integration repository.
Steps in Configuration
1. Goto service without party, right click->Assign a business system.
2. Choose the business system to be added.
3. Create a File Sender Service with communication channel for the same.
4. Create an idoc receiver channel under the business system.
7. The Idoc type( which data is to be written) is mentioned as inbound parameter.
8. Mention the logical Name in the Service->Adapter Specific Parameters of both the File Sender Service as well as the business system.
9. Make the Sender Agreement for theFile Sender with communication channel.
10.Create the Receiver Determination and Interface Determination for the business system.
11.Create the Receiver Agreement for the Business system.
Regards,
Vinod.

Similar Messages

How to send the spool output to the specific user during ALE distribution

Hi All
In ALE internal order Configuration done by BAPI Method SAVEREPLICA Business object BUS2075whenever user changed the internal order which is moved to the destination system because of change data setting in data element fields.
I want to know how to send the spool output of the changed internal order to the specific user during ALE distribution.
Please help me to reslove the above issue
Thanks & Regards
KRISHGUNA

Solved by myself

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

ALE distribution model - one message type to more than one recipient

Hello colleagues,
currently I'm working on an integration project between one SAP system and an e-shop system. The communication is established through IDOCs ( both inbound and outbound ). There is another system ( POS ) which is already integrated
with SAP via IDOCs also.
   Now I'm facing the following problem regarding distribution of transactional IDOCs ( orders, deliveries, etc. ): when assigning one message type ( for example DESADV - Delivery: Shipping notification ) to more than one external system in ALE distribution model I receive a message alerting that one message type can be send to only one recipient.
The distribution model is as follows:
Model Views
   SAP to POS
      SAPDEV ( the SAP system )
         POS ( the external POS system )
            DESADV
   SAP to E-SHOP
      SAPDEV ( the SAP system )
         E-SHOP ( the external e-shop system )
            DESADV
   Well, the system message is clear and I did the obvious: create a complete copy to the original message type and than assign it to the E-SHOP system ( the original message type is already used in integration between SAP and POS ).
As you can see I have found a workaround already but I think that it comes natural to SAP to communicate with other systems and to exchange same kind of documents to those systems and I can't believe that there isn't a standard solution for situation like this.
FYI I'm working on SAP ECC 6.0
Thanks in advance.
Wish you nice day and successful week ,
Vladimir

I believe when ePrint server has received the email, it made the necessary settings and configured the job for printing and then it went for "Reply All" option. So here it cannot send the print job to your personal email ID and the error came up.
The only option I can think of is add the printer email ID to your email contact list and give it a name like MyPrinter so you can remember easily , just like email contacts are added in Outlook.
Mark this post as answered so that others can find it useful.
Say "Thanks" by clicking the Kudos Star in the post that helped you.
Please mark the post that solves your problem as "Accepted Solution"

ALE Distribution Model

Hi,
I've created an ALE distribution model to process the interface concerning Set Up HR and Accounting. Initialy we make it all and distribute it to the receiving system (FI) and it seems to be ok. After that the funcional team generate some movements and the IDOC's were generated but they were not sent to the FI system. We've a look at tRFC and an error concerning user or password invalid appears, so i define again the user comunication and after a few adjustments to the model view we distribute it again to the FI system. When i execute it the following message appears : Model view HRFI-CFP has not been updated / Rreason: Distribution model is currently being processed.

Next step we delete the model view and created it again but the same error still remains.
Can anyone help me ???
Thanks is advance.
JMMatos

Hi
Distribution Model A model that describes the ALE message flow between logical systems.
Applications and the ALE distribution service layer use the model to determine receivers and to control the data distribution. The relationships between logical systems, message types, BAPIs and filters are defined in the distribution model.
Ex: The screen shot depicts customer distribution mode ALE_TRNG_Mar07.
Sender Logical System EC1CLNT800
Receiver Logical System SALES
Message Type CREMAS
No filter conditions defined.
This configuration step allows the installation of core ALE features on which data transfer activity will be based.
In the distribution model you can specify the messages to be sent to a given logical system. You can also define the conditions for the content and dispatch of messages in the filters.
The distribution model consists of one or more views that you can define
After creating the distribution model the model needs to be distributed to the receiver system.
Partner profiles need to be generated in both sender and receiver systems using transaction BD82 (automatically) or WE20 (manually).

File2idoc:Error in ALE distribution model for SendResponse

Hi,
I'm using XI to configure a file to idoc scenario.
Now in WE19 I could see relevant data,but in WE05 it showed the error status 51,and the detail message was "Error in ALE distribution model for SendResponse".
Do I have to create a distribution model in BD64?I did this ,but failed to create.

hi,
i dont think distribution model is required for inbound case.
just check the below configuration.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
chirag

Doubts on ALE and EDI

Hi all!
Could anyone please let me know the meaning of the following points which I came across in few resumes. I am new to Interfaces and just want to know few examples in detail on how an EDI and IDOC work? If anyone can explain any/few/all of the points below, it would be really very nice and helpful for many of us.
1. Involved in Master Data distribution for Vendor Master from Central Partner system using ALE Distribution Model.
2. Involved in EDI Configuration using Message Control, setting up the Message type, Access Sequence and Output Determination Procedure for Sales order.
3. Involved in the ALE configuration for maintaining Material Master Data, Customer Master Data and Vendor Master Data between two clients.
4. Assisted with troubleshooting EDI outbound interfaces and error message handling.
5. Extended IDOC for ORDERS05 for outbound processing.
6. Created sales order using standard IDOC (orders 05).
7. Monitoring and re-processing of the IDOC's
8. Created Message types and assigned it to IDOC type.
9. Created Process code and assigned it to Inbound Function Module.
Points assured!
Thanks!!

Hi Sekhar, regarding ALE this is some material.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User: MMUSER200 (This is the logon for dist.)
Client : 200
Password: MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as LGMODEL.
Sender as LG100.
Receiver as LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as LGMODEL.
Sender as LG200.
Receiver as LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as Mechanical Engineering
Material Type as Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time: WE07.
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.
Regarding IDOC,
Create Message Type (WE81)
Create Segment type (WE31)
Create IDOC Type (WE30)
Assign Segment type to Idoc Type (WE30)
Assign Idoc Type to Message Type (WE82)
Assign Function Module Mtype Idoc Type (WE57)
Create a Process Code (WE41-outbound, WE42-Inbound)
Enable Customized FM to ALE (BD51)
Assign these to Partner Profile (WE20)
check the following thread:
/message/2222912#2222912 [original link is broken]
http://help.sap.com/saphelp_erp2005vp/helpdata/en/e6/04c03e7856b300e10000000a114084/frameset.htm
Creation of Custom IDOc type and message Type
First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
take the Basis help to create them.
1.First create segments in WE31 Tcode with the required dataelements
2.Create the Basic Idoc Type in WE30
   release the Segments and IDOC type.
3.Create Message type in We81
4.Assign the message type to IDOC type in WE82 T code
5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for    Inbound) Outbound Fun module
7.Create Workflow setting if needed ..
8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
9.Define setting for fun module in BD51
10.In BD51 Define the settings for Fun module..
10.Assign the Processs Code to Fun mod`ule
hope this helps,
kindly reward if found helpful.
cheers,
Hema.
http://www.sapgenie.com/ale/why_ale.htm

Doubt in ale/idocs urjent

hi,
i have a doubt in ALE/IDOCS requirement is add a field to segment
in tcode BD53(reduce message type) after adding a field.
what configuration i need to do.

welcome to SDN.
Post this ABAP forum for quicker response.
ABAP Development
Regards
Raja

ALE/IDOC configurations?

Hi Experts,
Suppose i've two R/3 systems let say R1(Source system) and R2 (Target System). Now i want to send MATMAS05 IDOC from R1 to R2. Can anyone tell wht are ALE configuration's need to b done on both systems......plz give all Tcodes which are required at both systems with descriptions....
Pts will b rewarded to approraite answers
Regards
Faisal

Hi Friend ,
Please the process in steps .
MASTER DATA TRANSFERMATION BETWEEN 2 DIFF CLIENTS
 For this scenario Client 800 is the Sender and 810 is the receiving system
1. Creating Logical Systems
o Login using 800 client
o Go to T. Code SALE
o Expand Sending and Receiving Systems
o Expand Logical Systems
o Click on Define Logical System
o Click on New Entries
o Create STUD_S, STUD_R Logical Systems
o Save and come back
o Assign the STUD_S Logical System to client 800
o Assign the STUD_R Logical System to client 810
2. Creating the RFCs
o Go to T. Code SM59
o Expand R/3 Connections
o Enter RFC Name as STUD_S
o Connection Type as 3
o Language as EN
o Client as 800
o User as SAPUSER
o PWD as abap
o Target host as sap
o Click on Remote logon button to test the RFC
o Enter RFC Name as STUD_R
o Connection Type as 3
o Language as EN
o Client as 800
o User as SATISH
o PWD as abap
o Target host as sap
o Click on Remote logon button to test the RFC
3. Creating the Message Type
o Go to T. Code WE81
o Click on change, continue
o Click on New Entries button
o Give message type as ZBAPI_STUD_MAS and description
o Save and back
4. Creating the Segment
o Go to T. Code WE31
o Give segment name as ZBAPI_STUD_SEG
o Enter Short Text
o Enter the Field Name and Data Element in the text boxes
o Save, continue,
o Click on Edit -> Set Release.
5. Creating the Basic IDOC Object
o Go to T. code WE30
o Give obj. name as ZBAPI_STUD_IDOC
o Click on create
o Select create new radio button, give description and continue
o Select the IDOC obj name and click on create button
o Enter the segment name which is create earlier
o Select the check box if you want to make the segment mandatory
o Enter 1 in minimum number 99999 in maximum number, continue
o Save and back
o Click on Edit -> Set Release
6. Creating Customer Distribution Model
o Go to T. Code BD64
o Click on change and Create model view button
o Enter the short text and Technical name as ZSTUDENT
o Select the model and click on Add Message Type Button
o Give the Sender as STUD_S,
o Receiver as STUD_R,
o Message Type as ZBAPI_STUD_MAS
o Select the model view & click on Environment -> Generate Partner Profiles
o Select Transfer IDOC Immediately and Trigger Immediately radio buttons
o Click on Execute
o You should get a list in green color which means it executed successfully.
o Back to main screen, select the model view
o Click Edit->Model view->Distribute
o Click on continue
o You should get a list saying model view is distributed successfully.
7. Checking the Port
o Go to T. Code WE21
o Expand Transactional RFC
o Find the port from the list which is created using BD64 for STUD_R (Receiving system) RFC Destination.
8. Checking the Partner Profiles.
o Go to T. Code WE20
o Expand Partner Type LS
o Select the Partner profile STUD_R
o Double click on Message Type ZBAPI_STUD_MAS in Outbound parmtrs.
o Check Receiver Port is assigned correctly
o Check the Basic type as your Basic IDOC object.
9. Assigning the Message Type to Basic IDOC Object
o Go to T. Code WE82
o Click on Change & continue, New Entries button
o Give the Message type as ZBAPI_STUD_MAS
o Give Basic Type as ZBAPI_STUD_IDOC
o Release as 46C
o Save and back
10. Creating Inbound Function Module (Posting Program)
o Go to T. Code SE37
o Create a function Module IDOC_INPUT_ZBAPI_STUD_MAS
o Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.
o Import Parameters
INPUT_METHOD LIKE BDWFAP_PAR-INPUTMETHD
MASS_PROCESSING LIKE BDWFAP_PAR-MASS_PROC
NO_APPLICATION_LOG LIKE SY-DATAR
MASSSAVEINFOS LIKE MASSSAVINF
o Export Parameters
WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT
APPLICATION_VARIABLE LIKE BDWF_PARAM-APPL_VAR
IN_UPDATE_TASK LIKE BDWFAP_PAR-UPDATETASK
CALL_TRANSACTION_DONE LIKE BDWFAP_PAR-CALLTRANS
o Tables
IDOC_CONTRL LIKE EDIDC
IDOC_DATA LIKE EDIDD
IDOC_STATUS LIKE BDIDOCSTAT
RETURN_VARIABLES LIKE BDWFRETVAR
SERIALIZATION_INFO LIKE BDI_SER
o Exceptions
WRONG_FUNCTION_CALLED
o Source Code
DATA: FIRST_TRANC LIKE MARA_UEB-TRANC,
 ZBAPI_STUD_SEG like zbapi_stud.
DATA: ZBAPI_STUD LIKE ZBAPI_STUD.
DATA: I_ZBAPI_STUD LIKE ZBAPI_STUD.
DATA: C_TRUE VALUE 'X'.
DATA: C_FALSE VALUE ' '.
DATA: BEGIN OF T_IDOC_ROLLNO OCCURS 0,
 DOCNUM LIKE EDIDC-DOCNUM,
 ROLLNO LIKE ZBAPI_STUD-ROLLNO,
 END OF T_IDOC_ROLLNO.
DEFINE APPEND_RESFIELDS.
 PERFORM APPEND_RES_FIELDS TABLES T_MFIELDRES
 T_RES_FIELDS
 USING &1
 COUNTER-D_IND.
END-OF-DEFINITION.
DATA: I_MARA_UEB LIKE MARA_UEB.
DATA: I_ZSTUD_UEB LIKE ZBAPI_STUD.
DATA: I_MAKT_UEB LIKE MAKT_UEB.
DATA: I_MARC_UEB LIKE MARC_UEB.
DATA: I_MARD_UEB LIKE MARD_UEB.
DATA: I_MFHM_UEB LIKE MFHM_UEB.
DATA: I_MARM_UEB LIKE MARM_UEB.
DATA: I_MEAN_UEB LIKE MEA1_UEB.
DATA: I_MBEW_UEB LIKE MBEW_UEB.
DATA: I_STEU_UEB LIKE STEU_UEB.
DATA: I_STEUMM_UEB LIKE STEUMM_UEB.
DATA: I_MLGN_UEB LIKE MLGN_UEB.
DATA: I_MLGT_UEB LIKE MLGT_UEB. " //br010797 neu zu 4.0
DATA: I_MPGD_UEB LIKE MPGD_UEB.
DATA: I_MPOP_UEB LIKE MPOP_UEB.
DATA: I_MVEG_UEB LIKE MVEG_UEB.
DATA: I_MVEU_UEB LIKE MVEU_UEB.
DATA: I_MVKE_UEB LIKE MVKE_UEB.
DATA: I_MPRW_UEB LIKE MPRW_UEB.
DATA: I_LTX1_UEB LIKE LTX1_UEB.
DATA: HELP_MARC_UEB LIKE MARC_UEB.
DATA: T_MARA_UEB LIKE MARA_UEB OCCURS 0.
DATA: T_MAKT_UEB LIKE MAKT_UEB OCCURS 0.
DATA: T_MARC_UEB LIKE MARC_UEB OCCURS 0.
DATA: T_MARD_UEB LIKE MARD_UEB OCCURS 0.
DATA: T_MFHM_UEB LIKE MFHM_UEB OCCURS 0.
DATA: T_MARM_UEB LIKE MARM_UEB OCCURS 0.
DATA: T_MEAN_UEB LIKE MEA1_UEB OCCURS 0.
DATA: T_MBEW_UEB LIKE MBEW_UEB OCCURS 0.
DATA: T_STEU_UEB LIKE STEU_UEB OCCURS 0.
DATA: T_STEUMM_UEB LIKE STEUMM_UEB OCCURS 0.
DATA: T_MLGN_UEB LIKE MLGN_UEB OCCURS 0.
DATA: T_MLGT_UEB LIKE MLGT_UEB OCCURS 0. " //br010797 neu zu 4.0
DATA: T_MPGD_UEB LIKE MPGD_UEB OCCURS 0.
DATA: T_MPOP_UEB LIKE MPOP_UEB OCCURS 0.
DATA: T_MVEG_UEB LIKE MVEG_UEB OCCURS 0.
DATA: T_MVEU_UEB LIKE MVEU_UEB OCCURS 0.
DATA: T_MVKE_UEB LIKE MVKE_UEB OCCURS 0.
DATA: T_MPRW_UEB LIKE MPRW_UEB OCCURS 0.
DATA: T_LTX1_UEB LIKE LTX1_UEB OCCURS 0.
Internal fields/ tables
DATA: FLAG_ERROR_HAPPENED.
DATA: flag_material_exists. "//br210397 zu 4.0 keine Verwendung mehr
DATA: FLAG_EXIT_TO_BE_DONE.
DATA: HELP_TABIX LIKE SY-TABIX.
DATA: HELP_TRANC LIKE MARA_UEB-TRANC.
DATA: HELP_ALAND LIKE STEU_UEB-ALAND.
DATA: HELP_VKORG LIKE MVKE-VKORG.
DATA: HELP_WERKS LIKE T001W-WERKS.
DATA: HELP_LFDNR LIKE STEU_UEB-LFDNR.
DATA: LAST_MARC_TRANC LIKE MARA_UEB-TRANC.
DATA: LAST_MLGN_TRANC LIKE MARA_UEB-TRANC. " //br010797 neu zu 4.0
DATA: LAST_TEXT_TRANC LIKE MARA_UEB-TRANC.
DATA: CURRENT_TABIX LIKE SY-TABIX.
DATA: GENERAL_SUBRC LIKE SY-SUBRC.
DATA: HELP_FACTOR TYPE P DECIMALS 3.
DATA: USER_SEGMENTS LIKE EDIDD OCCURS 0 WITH HEADER LINE. " insert
DATA: CUST_SEGMENT LIKE EDIDD.
DATA: I_MFIELDRES LIKE MFIELDRES.
DATA: I_MERRDAT LIKE MERRDAT.
DATA: I_EDIDD LIKE EDIDD.
 " //br neu zu 3.1g
DATA: T_RES_FIELDS LIKE DELFIELDS OCCURS 0 WITH HEADER LINE.
DATA: T_MFIELDRES LIKE MFIELDRES OCCURS 0.
DATA: T_MERRDAT LIKE MERRDAT OCCURS 0.
DATA: T_EDIDD LIKE EDIDD OCCURS 0.
DATA: BEGIN OF t_matnr OCCURS 0, "//br210397 zu 4.0
 matnr LIKE mara-matnr, " wird nicht mehr verwendet
 END OF t_matnr. "
DATA: BEGIN OF COUNTER,
 TRANC LIKE MARA_UEB-TRANC,
 D_IND LIKE MARA_UEB-D_IND,
 END OF COUNTER.
DATA: BEGIN OF t_idoc_tranc OCCURS 0, " 4.0
 docnum LIKE edidc-docnum, "
 tranc LIKE mara_ueb-tranc, "
 END OF t_idoc_tranc. "
DATA T_IDOC_TRANC LIKE MATIDOCTRANC OCCURS 0 WITH HEADER LINE."
DATA: FLAG_FITS.
DATA: APPLICATION_SUBRC LIKE SY-SUBRC.
DATA FLAG_MUSS_PRUEFEN LIKE SY-DATAR.
DATA MAX_ERRORS LIKE T130S-ANZUM. " 4.0
note 419281
DATA : FLG_MASS.
CLEAR : FLG_MASS.
FIELD-SYMBOLS: . " 4.0
ALE-distribution unity : IDOC status set by locking "note0361838
data: "note0361838
 it_dsp_idocstat like bdidocstat "note0361838
 occurs 0 with header line. "note0361838
Initialize data - general
REFRESH T_MFIELDRES.
REFRESH T_IDOC_TRANC.
REFRESH T_IDOC_TRANC. "JH/02.02.98/4.0C KPr100004993
REFRESH t_idoc_tranc_segment. " //br 40 : unnötig
REFRESH matnr_tranc. " -"-
REFRESH t_matnr.
COUNTER-TRANC = 1.
COUNTER-D_IND = 1.
REFRESH T_MARA_UEB.
REFRESH T_MAKT_UEB.
REFRESH T_MARC_UEB.
REFRESH T_MARD_UEB.
REFRESH T_MFHM_UEB.
REFRESH T_MARM_UEB.
REFRESH T_MEAN_UEB.
REFRESH T_MBEW_UEB.
REFRESH T_STEU_UEB.
REFRESH T_STEUMM_UEB.
REFRESH T_MLGN_UEB.
REFRESH T_MLGT_UEB. " //br010797 neu zu 4.0
REFRESH T_MPGD_UEB.
REFRESH T_MPOP_UEB.
REFRESH T_MVEG_UEB.
REFRESH T_MVEU_UEB.
REFRESH T_MVKE_UEB.
REFRESH T_MPRW_UEB.
REFRESH VKORG_ALAND.
REFRESH WERKS_ALAND.
CLEAR APPLICATION_SUBRC.
REFRESH T_MERRDAT.
Check if right function is called
READ TABLE IDOC_CONTRL INDEX 1.
IF SY-SUBRC <> 0.
 EXIT.
ELSE.
 IF IDOC_CONTRL-IDOCTP <> 'ZBAPI_STUD_IDOC'.
 RAISE WRONG_FUNCTION_CALLED.
 ENDIF.
ENDIF.
LOOP AT IDOC_CONTRL.
Initialize data - per IDOC
t_idoc_tranc-docnum = counter-tranc.
 T_IDOC_TRANC-DOCNUM = IDOC_CONTRL-DOCNUM.
 T_IDOC_TRANC-FIRST_TRANC_IDOC = COUNTER-TRANC + 2.
 APPEND T_IDOC_TRANC.
Select segments which belong to IDOC
 REFRESH T_EDIDD.
 LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
 APPEND IDOC_DATA TO T_EDIDD.
 ENDLOOP.
 BUSINESS TRANSACTION EVENT (header / data) "note0388000
 call function 'OPEN_FI_PERFORM_MGV00200_E' "note0388000
 exporting "note0388000
 idoc_header = idoc_contrl "note0388000
 FLG_APPEND_STATUS = 'X' "note0388000
 tables "note0388000
(DEL) idoc_data = idoc_data "note0388000 note0418561
 idoc_data = t_edidd "note0418561
 idoc_status = idoc_status "note0388000
 exceptions "note0388000
 others = 1. "note0388000
 if sy-subrc = 1. "note0388000
 continue. "note0388000
 endif. "note0388000
Within one IDOC: loop through data segments:
Prepare internal tables for the current material
 LOOP AT T_EDIDD INTO IDOC_DATA.
 Transform from CoreData to Normal Data if necesary
 CASE IDOC_DATA-SEGNAM.
 WHEN 'E1MARAC'.
*--COMMENTED BY SATISH
 PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.
 WHEN 'E1MAKTC'.
 PERFORM MOVE_E1MAKTC_TO_E1MAKTM USING IDOC_DATA.
*--COMMENTES ENDED BY SATISH
 WHEN 'ZBAPI_STUD_SEG'.
 PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.
 CLEAR I_ZBAPI_STUD.
Second: Move E1MARAC into E1MARAM
 I_ZBAPI_STUD = IDOC_DATA-SDATA.
Third: Move E1MARAM back into IDOC-line
 IDOC_DATA-SDATA = I_ZBAPI_STUD.
 IDOC_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.
 ENDCASE.
 CURRENT_TABIX = SY-TABIX.
 COUNTER-D_IND = COUNTER-D_IND + 1.
 COUNTER-TRANC = COUNTER-TRANC + 2.
 CASE IDOC_DATA-SEGNAM.
 WHEN 'ZBAPI_STUD_SEG'.
 Initialize data - per material
 COUNTER-D_IND = 1.
 FIRST_TRANC = COUNTER-TRANC.
 interpret segment
 ZBAPI_STUD_SEG = IDOC_DATA-SDATA.
 MOVE-CORRESPONDING ZBAPI_STUD TO I_ZSTUD_UEB.
 T_IDOC_ROLLNO-DOCNUM = IDOC_CONTRL-DOCNUM.
 T_IDOC_ROLLNO-ROLLNO = I_ZSTUD_UEB-ROLLNO.
 APPEND T_IDOC_ROLLNO.
 ENDCASE.
 if not ZBAPI_STUD_SEG is initial.
 ZBAPI_STUD-MANDT = ZBAPI_STUD_SEG-MANDT.
 ZBAPI_STUD-ROLLNO = ZBAPI_STUD_SEG-ROLLNO.
 ZBAPI_STUD-FNAME = ZBAPI_STUD_SEG-FNAME.
 ZBAPI_STUD-LNAME = ZBAPI_STUD_SEG-LNAME.
 INSERT ZBAPI_STUD FROM ZBAPI_STUD_SEG.
 COMMIT WORK.
 ENDIF.
*-- ALE ditribution unity : update IDOC status "note03618
 LOOP AT it_dsp_idocstat. "note036
 LOOP AT IDOC_STATUS WHERE DOCNUM = it_dsp_idocstat. "note036
 DELETE idoc_status INDEX sy-tabix. "note036
 ENDLOOP. "note036
 APPEND it_dsp_idocstat TO idoc_status. "note036
 ENDLOOP. "note036
*--GENERATING THE IDOC STATUS
PERFORM HANDLE_ERROR_EXT " //br40
 TABLES "
 IDOC_CONTRL "
 IDOC_STATUS "
 RETURN_VARIABLES "
 T_MERRDAT "
 T_IDOC_TRANC "
 T_IDOC_ROLLNO "JH/4.0C/KPr100004993
 USING "
 GENERAL_SUBRC "
 NO_APPLICATION_LOG "
 MASSSAVEINFOS "wk/40c
 CHANGING "
 WORKFLOW_RESULT. "
 PERFORM HANDLE_ERROR
 TABLES
 IDOC_CONTRL
 IDOC_STATUS
 RETURN_VARIABLES
 T_MERRDAT
 T_IDOC_ROLLNO "JH/4.0C/KPr100004993
 USING
 APPLICATION_SUBRC
 CHANGING
 WORKFLOW_RESULT.
SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124
React on general error
DATA: I_MERRDAT LIKE MERRDAT.
IF GENERAL_SUBRC <> 0.
 I_MERRDAT-MSGTY = 'E'.
 I_MERRDAT-MSGID = SY-MSGID.
 I_MERRDAT-MSGNO = SY-MSGNO.
 I_MERRDAT-MSGV1 = SY-MSGV1.
 I_MERRDAT-MSGV2 = SY-MSGV2.
 I_MERRDAT-MSGV3 = SY-MSGV3.
 I_MERRDAT-MSGV4 = SY-MSGV4.
 APPEND I_MERRDAT TO T_MERRDAT.
ENDIF.
LOOP AT T_MERRDAT INTO I_MERRDAT
 WHERE MSGTY = 'S' "success
 OR MSGTY = 'D' "dummy
 OR MSGTY = 'I' "Information " //br011097 zu 3.1I
 OR MSGTY = 'H' "dummy " 4.0
 OR MSGTY = 'W'. "warning
 DELETE T_MERRDAT.
ENDLOOP.
 ENDLOOP.
ENDLOOP.
ENDFUNCTION.
*& Form handle_error_ext
FORM HANDLE_ERROR_EXT
 TABLES
 IDOC_CONTRL STRUCTURE EDIDC
 IDOC_STATUS STRUCTURE BDIDOCSTAT
 RETURN_VARIABLES STRUCTURE BDWFRETVAR
 T_MERRDAT STRUCTURE MERRDAT
 IDOC_TRANC STRUCTURE MATIDOCTRANC
JH/02.02.98/4.0C KPr100004993 (Anfang)
 T_IDOC_ROLLNO STRUCTURE T_IDOC_ROLLNO
JH/02.02.98/4.0C KPr100004993 (Ende)
 USING
 GENERAL_SUBRC LIKE SY-SUBRC
 NO_APPLICATION_LOG LIKE SY-DATAR
 MASSSAVEINFOS LIKE MASSSAVINF
 CHANGING
 WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT.
DATA FLAG_ERROR_HAPPENED.
DATA I_MERRDAT LIKE MERRDAT.
DATA IDOC_INDEX_2_SUBRC LIKE SY-SUBRC.
DATA AL_HANDLES TYPE BAL_T_LOGH. "//br99
SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124
React on general error
IF GENERAL_SUBRC <> 0.
 REFRESH T_MERRDAT.
i_merrdat-tranc = 0. " //br261197
 READ TABLE IDOC_TRANC INDEX 1. " zu 40b
 I_MERRDAT-TRANC = IDOC_TRANC-FIRST_TRANC_IDOC. "
 I_MERRDAT-MSGTY = 'E'.
 I_MERRDAT-MSGID = SY-MSGID.
 I_MERRDAT-MSGNO = SY-MSGNO.
 I_MERRDAT-MSGV1 = SY-MSGV1. I_MERRDAT-MSGV2 = SY-MSGV2.
 I_MERRDAT-MSGV3 = SY-MSGV3. I_MERRDAT-MSGV4 = SY-MSGV4.
 APPEND I_MERRDAT TO T_MERRDAT.
ENDIF.
DATA: C_TRUE,
 C_FALSE VALUE 'X'.
If error happened ==> Rollback whole work....
LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY NA 'SDHWI'.
 EXIT.
ENDLOOP.
IF SY-SUBRC = 0.
 FLAG_ERROR_HAPPENED = C_TRUE.
 ROLLBACK WORK.
ELSE.
 FLAG_ERROR_HAPPENED = C_FALSE.
ENDIF.
Set IDOC status
two cases:
single IDOC-processing: ==> error can be written in IDOC status
package processing ==> anononymous "package error" for all IDOCs
READ TABLE IDOC_CONTRL INDEX 2.
IDOC_INDEX_2_SUBRC = SY-SUBRC.
IF SY-SUBRC = 0.
 IF 1 = 2. "//br40
 MESSAGE E051(B1). "
 ENDIF. "
 CLEAR I_MERRDAT.
 I_MERRDAT-MSGID = 'B1'.
 I_MERRDAT-MSGTY = 'E'.
 I_MERRDAT-MSGNO = '051'.
ENDIF.
IF IDOC_INDEX_2_SUBRC NE 0 OR FLAG_ERROR_HAPPENED = C_FALSE.
Nur in diesen Fällen wird Application Log geschrieben
Delete all Successes and Dummy records from t_merrdat
DELETE t_merrdat WHERE msgty = 'S' "success " testweise
 OR msgty = 'D'. "dummy "
 LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY = 'D'. "
 I_MERRDAT-MSGTY = 'S'. "
 MODIFY T_MERRDAT FROM I_MERRDAT. "
 ENDLOOP. "
ENDIF.
WORKFLOW_RESULT = 0.
LOOP AT IDOC_CONTRL.
Set IDOC status
 CLEAR IDOC_STATUS.
 IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
 IF FLAG_ERROR_HAPPENED = C_FALSE.
Application log
 PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC
 T_MERRDAT
 IDOC_STATUS
 USING IDOC_CONTRL
 FLAG_ERROR_HAPPENED
 NO_APPLICATION_LOG
 MASSSAVEINFOS
 AL_HANDLES.
 idoc_status-status = '53'. "OK!
 APPEND idoc_status.
JH/02.02.98/4.0C KPr100004993 (Anfang)
 Fill Return variables
 CLEAR RETURN_VARIABLES.
 RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
 RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
 APPEND RETURN_VARIABLES.
 Verknüpfungseintrag anlegen
 READ TABLE T_IDOC_ROLLNO WITH KEY ROLLNO = IDOC_CONTRL-DOCNUM
 BINARY SEARCH.
 IF SY-SUBRC = 0.
 RETURN_VARIABLES-DOC_NUMBER = T_IDOC_ROLLNO-ROLLNO.
 RETURN_VARIABLES-WF_PARAM = 'Appl_Objects'.
 APPEND RETURN_VARIABLES.
 ENDIF.
JH/02.02.98/4.0C KPr100004993 (Ende)
 ELSE.
 IF IDOC_INDEX_2_SUBRC NE 0.
Application Log
 PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC
 T_MERRDAT
 IDOC_STATUS
 USING IDOC_CONTRL
 FLAG_ERROR_HAPPENED
 NO_APPLICATION_LOG
 MASSSAVEINFOS
 AL_HANDLES.
 ELSE.
 IDOC_STATUS-MSGID = I_MERRDAT-MSGID.
 IDOC_STATUS-MSGTY = I_MERRDAT-MSGTY.
 IDOC_STATUS-MSGNO = I_MERRDAT-MSGNO.
 IDOC_STATUS-MSGV1 = I_MERRDAT-MSGV1.
 IDOC_STATUS-MSGV2 = I_MERRDAT-MSGV2.
 IDOC_STATUS-MSGV3 = I_MERRDAT-MSGV3.
 IDOC_STATUS-MSGV4 = I_MERRDAT-MSGV4.
 IDOC_STATUS-STATUS = '51'. "ERROR!
 APPEND IDOC_STATUS.
 ENDIF.
 Fill Return variables
 CLEAR RETURN_VARIABLES.
 RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
 return_variables-wf_param = c_wf_par_processed_idocs.
 RETURN_VARIABLES-WF_PARAM = 'Error_IDOCs'.
 APPEND RETURN_VARIABLES.
 WORKFLOW_RESULT = 99999.
 ENDIF.
APPEND idoc_status.
ENDLOOP.
IF NO_APPLICATION_LOG IS INITIAL.
 CALL FUNCTION 'BAL_DB_SAVE' "//br99
 EXPORTING
 I_IN_UPDATE_TASK = ' '
 I_SAVE_ALL = ' '
 I_T_LOG_HANDLE = AL_HANDLES.
 EXCEPTIONS
 LOG_NOT_FOUND = 1
 SAVE_NOT_ALLOWED = 2
 NUMBERING_ERROR = 3
 OTHERS = 4.
 CALL FUNCTION 'BAL_GLB_MEMORY_REFRESH' "//br99
 EXPORTING
 I_AUTHORIZATION =
 I_REFRESH_ALL = ' '
 I_T_LOGS_TO_BE_REFRESHED = AL_HANDLES.
 EXCEPTIONS
 NOT_AUTHORIZED = 1
 OTHERS = 2
ENDIF.
ENDFORM. " handle_error
Save, check and activate
11. Assigning the Inbound Function Module to Basic Type & Message Type
o Go to T. Code WE57
o Click on change, continue, continue and New Entries Button
o Enter the Module as IDOC_INPUT_ZBAPI_STUD_MAS
o Type as F
o Basic Type as ZBAPI_STUD_IDOC
o Message Type as ZBAPI_STUD_MAS.
o Direction as 2
o Save and back
Now Login in 810 client
12. Assigning the Inbound Function Module in ALE Table
o Go to T. Code BD51
o Click on continue, New Entries button
o Give the Inbound Function Module IDOC_INPUT_ZBAPI_STUD_MAS
o Give Input t. as 0 (zero)
o Save and back
13. Creating Process Code
o Go to T. Code WE42
o Click on Change, New Entries Button
o Give Process Code name as ZSTUD, give Description & Save
o Select Processing with ALE Services Radio button
o Select Processing by Function Module Radio button
o Click the ALE Table (arrow Icon) in Identification
o Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS
o Give maximum number of repeats 0
o Save and back, back
o Select the process code from the list & click on Logical Messages Icon
o Give the Message Type as ZBAPI_STUD_MAS
o Save & Back, Save & Back, Save & Back
14. Changing the Customer Distribution model in Receiving system
o Go to T. Code BD64
o Click on change and Create model view button
o Select the model view & click on Environment -> Generate Partner Profiles
o Select Transfer IDOC Immediately and Trigger Immediately radio buttons
o Click on Execute
o You should get a list in green color which means it executed successfully.
15. Assigning the Process Code to Message Type in Receiving System
o Go to T. Code WE20
o Expand Partner Type LS
o Select the Partner Profile STUD_S
o Double click on Message Type ZBAPI_STUD_MAS in Inbound parmtrs.
o Give the Process Code as ZSTUD
o Click on Trigger Immediately Radio button
o Save & Back
o Save & Back
16. Creating the Selection Program (Outbound Program)
 Login in client 800.
 Go to T. Code SE38
 Create a Report Program as ZSTUD_SEND with the following code
REPORT ZSTUD_SEND
 NO STANDARD PAGE HEADING.
TABLES: ZBAPI_STUD.
DATA: IT_STUD LIKE ZBAPI_STUD OCCURS 0 WITH HEADER LINE.
SELECTION-SCREEN:BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-H01.
SELECT-OPTIONS: S_ROLLNO FOR ZBAPI_STUD-ROLLNO.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN:BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-H02.
PARAMETERS: P_MESTYP LIKE EDIDC-MESTYP,
 P_RCVPRN LIKE TBDLST-LOGSYS.
SELECTION-SCREEN:END OF BLOCK B2.
SELECTION-SCREEN:END OF BLOCK B1.
START-OF-SELECTION.
PERFORM CREATE_STUDENT.
PERFORM CREATE_IDOC.
*& Form CREATE_STUDENT
 sending student
FORM CREATE_STUDENT.
SELECT * FROM ZBAPI_STUD
 INTO TABLE IT_STUD
 WHERE ROLLNO IN S_ROLLNO.
ENDFORM. " CREATE_STUDENT
*& Form CREATE_IDOC
 IDOC Creation
FORM CREATE_IDOC.
DATA : IMAS_DATA LIKE EDIDD OCCURS 10 WITH HEADER LINE,
 IMAS_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE,
 ICOM_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE.
IMAS_CON-RCVPRT = 'LS'.
IMAS_CON-RCVPRN = P_RCVPRN.
IMAS_CON-IDOCTP = 'ZBAPI_STUD_IDOC'.
IMAS_CON-MESTYP = P_MESTYP.
IMAS_CON-DIRECT = 1.
APPEND IMAS_CON.
LOOP AT IT_STUD.
IMAS_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.
IMAS_DATA-SDATA = IT_STUD.
APPEND IMAS_DATA.
ENDLOOP.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
 EXPORTING
 MASTER_IDOC_CONTROL = IMAS_CON
 OBJ_TYPE = ''
 CHNUM = ''
 TABLES
 COMMUNICATION_IDOC_CONTROL = ICOM_CON
 MASTER_IDOC_DATA = IMAS_DATA
 EXCEPTIONS
 ERROR_IN_IDOC_CONTROL = 1
 ERROR_WRITING_IDOC_STATUS = 2
 ERROR_IN_IDOC_DATA = 3
 SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
 OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK.
LOOP AT ICOM_CON.
WRITE :/ 'IDOC: ', ICOM_CON-DOCNUM, 'CREATED SUCCESSFULLY'.
ENDLOOP.
ENDFORM. " CREATE_IDOC
17. Transferring the student records from 800 to 810 client
 Execute Report Program ZSTUD_SEND
 Give the Range of Roll Nos to Transfer
 Give Message Type as ZBAPI_STUD_MAS
 Give Receiver Logical system as STUD_R
 Execute
 You should get the IDOC Number
 Take the IDOC Number and go to T. Code WE05 & Execute
 In Outbox you can see the IDOC Status
 Select the status record in left side window
 Double click on the Status record in right side window
 You can see the Control Record, Data Record and Status Records for that IDOC
 If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully.
Now Login in 810 client
 Go to T. Code WE05 & Execute
 You can see the status record in left side window
 If the status no is 53 and color is green, it means the IDOC is Posted to Application successfully.
 You can see the Log Information by double clicking on the status record in right side window.
 Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC
 Now go to T. Code SE16
 Give the table name ZBAPI_STUD & press F7
 See the contents of the table
 The table is updated with the students records transferred from 800 client with our selection program.
Reward if useful
Regrds
Jagadeesh.G

Query related to filter group on matnr created in ALE distribution model

Hi All,
I have query related to filter group on matnr created in ALE distribution model.
I have created a filter group on matnr in ALE distribution model and put the value E* ( purpose is that all the material number started with E should be triggered in case of any changes in the material).But it is not working.
Can anybody suggest the solution for this i.e how to capture E* value for the material master changes and should trigger idoc using change pointer using BD21.
Thanks & Regards
Prabhat

Unfortunately, you cannot filter using wildcards or exclusions. You have to explicitly list each allowed value in its entirety.
In my opinion, the simplest solution would be to copy function MASTERIDOC_CREATE_SMD_MATMAS, modify it to handle your custom filtering and update the message type entry in transaction BD60.

ALE/ IDOC CONFIGURATION OBJECT

IT'S URGENT
I NEED AN OBJECT IN ALE/IDOC CONFIGURATION SETTINGS

Hi Viji.
I can provide you a link which deals with precise material for ALE/IDOC configuration.
This link has just 1 page, but very good configurations.
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wsadapters.jca_sap.doc/doc/csap_depl_config_serv.html
Inside if you want Outbound or Inbound settings, choice is to be made.
<removed by moderator>
Regards
Harsh
Edited by: Mike Pokraka on Aug 6, 2008 10:56 AM

Error executing BAPI attached to ALE Distribution Model

Hi experts,
I am executing BAPI_EXCHANGERATE_SAVEREPLICA which has been included in an ALE distribution model as I wish to replicate exchange rates from my source client to a number of remote clients.
When I execute the BAPI I get an information message back in the bapi return code as follows "one table record planned for update". Does anyone know what this means? I would have expected idocs to have been created and sent across to the target clients and for the BAPI to have been executed in the target system but nothing has happened. I have released the method (BAPI) and tried various options on the partner profile but still get the same message returned when I call the BAPI.
Any help on executing this BAPI via ALE would be much appreciated.
Thanks
Adrian

This is information message that informs you that the selected row may be updated. Then when you call BAPI_TRANSACTION_COMMIT the rows will be updated.

Message type US for ALE distribution

I want to create an outbound IDOC using ALE distribution.
I have to assign Partner type as 'US' - user. Can anyone give me some input. I got the error when trying to do the same
" No partner profiles (message control) maintained
Message no. B1127 Diagnosis No IDOC partner profiles have been created for the message control for
 for application EF, condition key ZNBR and change message '' with
 partner type 'LS' and partner role ' '.
Procedure Please create the partner profiles for the logical system that should
 contain the IDOC. You can either generate them from the ALE model or
 create them manually.
Step by step will be helpfull.
Thanks

Hi Preethi,
You can use this program RBDCUS15 to generate outbound partner profile.
Also you use distribution model (t/code BD64) as well.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

ALE Distribution model customisation question.

Hi,
How essential is it to undertake the SRM ALE Distribution model config prior to making the changes to the R/3 backend tables, e.g. CRMCONSUM, CRMPAROLTP, SMOFPARSFA? The SAP SRM config guide does not indicate the whether or not the ALE config needs to be undertaken before or after the R/3 middleware config.
Please can some one clarify this.
Thank you.
Steve,

Hi Stewe
ALE Idoc Settings are required for Invoice, Good Receipt and PO Commitment.
But CRM settings are required for transfering your Business Object and Customizing object.
Both are not related each other.
regards
Muthu

ALE/IDOC configuration study Material

Hi All,
Anyone come across ALE/IDOC configuration study Material which consists of
ONLY ONE PAGE. If YES, Please pass it on.
Points Assured \[but not given. Dont write such statements here anyway!\]
Regards,
Viji.
Edited by: Jan Stallkamp on Aug 6, 2008 2:26 PM

Hi Viji.
I can provide you a link which deals with precise material for ALE/IDOC configuration.
This link has just 1 page, but very good configurations.
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wsadapters.jca_sap.doc/doc/csap_depl_config_serv.html
Inside if you want Outbound or Inbound settings, choice is to be made.
<removed by moderator>
Regards
Harsh
Edited by: Mike Pokraka on Aug 6, 2008 10:56 AM

Doubts on ALE Distribution Configuration

Similar Messages

Maybe you are looking for