ALE Process code

HI friends.....
1.if we create partner profile we need two systems or not
2. where these partner profile are stored(this means outbound partner profile table)
3. will we create process code both inbound and outbound?
4. will we create customize process code?
Stand alone program need to create process code
5. how to create the process code?
please tel me...
thanks & regards
mani

Hi,
1.if we create partner profile we need two systems or not?
    Ans. Yes we need two systems.
2. where these partner profile are stored(this means outbound partner profile table)
   TMSG1 Logical Messages and Process Codes in Outb. Procg
   TMSG2 Logical Messages and Process Codes in Inb. Procg
3. will we create process code both inbound and outbound?
     Process code is nothing but to identify the FM or Standalone program to
    create or process the idocs.
    So to create Idoc we need one program which is assigned to a FM or Program.
   and to process Idoc we need one program which is assigned to a FM or
   Program.
4. will we create customize process code? Yes
   Stand alone program need to create process code --Yes
5. how to create the process code?
    tcode WE41 --Outbound process code
             WE42---Inbound Process code
Click on new entries.
Don't forget to reward if useful

Similar Messages

What is a process code in ale idoc

what is a process code in ale idoc,what is the purpose of Process code.

Hi,
     Let me tell some scenario then u would be able to understand what a process code is-------
In ALE ie, the data requested system is receiver and the data already presented system is sender ie, from where we are having the data,
here in sender side----
       we need a program to tranfer required data into idoc--( idoc is just a data container )    in sender side this program logic is in a function module it is configured in we41.
         ie this will transfer the data from database to idoc----in sender side it is a process code
and in receiver side after receiving the data we have to post it in database again program needed it is also ie the required code is also in function module it is configured in we42
it is about receiver side f.m or simply process code
okkkkkkkkkkkk

Need of Process code in ALE Inbound Processing?

Hi All,
What is the need of process code in ALE Inbound Processing? Why do we need to reach the function module through process code? we can as well directly point to function module.

Hi Ravi,
Please chcek this link perhaps it may help.
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/frameset.htm
Regards,
Ferry Lianto

Process Code for Message Type LOIPRO(in ALE/IDOCS)

Hi all,
I have to implement Production order Interface(create Production order,change Production order etc).The requirement is for eg:,I created one production order and posted it;it should get reflected in the recieving system.Does anyone know the process code for LOIPRO.I checked it in we42,WE64 and even the tables TEDE1 and TEDE2.But its not available.Process code and function module is necessary to continue with WE20.
Thanking you in advance,
anjaly

Hi
it may sound like not good news, but I think the answer is described in OSS Note 198252 - Special features of POI message category LOI*.
There all LOI* idocs are mentioned and then they say:
The message categories named are part of the POI (Production Optimization interface) interface.This interface and the message categories contained in it were developed for the transfer to non-R/3 systems.Therefore, an inbound processing in the R/3 system is not planned.The message categories are transferred via separate transactions / reports of the POI interface (Transactions POIM, POIT).Functions which exceed these transactions are not supported.For this reason, the above-mentioned ALE functions cannot be used for the message categories described.
So, in short, there is no inbound process code for LOIPRO.
Inbound processing then should be done through self-developed programs / idocs, calling BAPI-s (for example).
Regards,
Joe
Edited by: Joseph Yasman on Jun 30, 2009 1:46 PM

Problem in ALE inbound With process code

i want to give a function module to the in bound process code in transaction WE42 but i am not able to give the function module name .after giving the function module name if i say save system giving message "The ALE table is not yet maintained for process code ZTEST".

Hi,
This are the steps which involoves the Idoc processing .
For ur query, check the bold letters .. do that part . it will solve ur problem
Create Idoc type Transaction WE30.
Idoc type Idoc segments
Z_idoc
Create Message Type Transaction WE81.
Message type
z_msg
Assign Message Type to Idoc type Transaction WE82.
Idoc type Message type
z_idoc z_msg
<b>Create a function module through SE37
z_idoc_input
Assign characteristic of function module BD51
Assign fn module to Idoc type and Message Type WE57
Idoc type Message type Fn Module
z_idoc z_msg z_idoc_input
Create Inbound process code and assign inbound function module Transaction WE42.
Process code Inbound function module
zcode z_idoc_input</b>
Create a distribution Model - Transaction BD64
Create distribution model for distribution of messages
with the message type of z_msg
Update inbound parameters of the Partner profile Transaction WE20
For the Logical system A for the above message type update the partner profile
inbound parameter and specify the process code of zcode.
For Outbound ALE Configurations: (Example)
IDoc definitions and necessary ALE configurations settings for the outbound .
Create Idoc segments Transaction WE31.
Create Idoc type Transaction WE30.
Create Message Type Transaction WE81.
Assign Message Type to Idoc type Transaction WE82.
Create a distribution Model - Transaction BD64.
Reward points if it is Useful.
Thanks,
Manjunath MS

. What is a process code in ALE

. What is a process code in ALE
could u plz explain clearly

hi,
a process code represent function mod.,
Process code will come in to picture when you deal with IDOCS .. you need to assign a code which internally will have a Function module or a Include, that will have entire code to run your bussiness for an IDOC or EDI or ALE.
reward useful points,
siva
Message was edited by:
Shan

ALE INBOUND Process Code

Hi,
In ALE INBOUND Process Code Apart from the Function Module name, what are the important things to be filled up while creating that InBound process code in WE42. What is the importance of those? what is the importance of Object Attributes in that?

Hi Mahesh check this may be useful to you
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.
Link Message Type to Function Module (WE57) Client independent
u2022 Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Define FM settings (BD51) Client independent
u2022 Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
u2022 Click on New entries
u2022 Enter 0 for mass processing in the output column
u2022
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:
u2022 Log on to the appropriate receiving system client
u2022 Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
u2022 Choose Inbound with ALE service
u2022 Choose Processing with function module
u2022 Click on Processing with function module and choose create icon
u2022 Click on New Entries
u2022 Type in process code XXXXXXX and give it a description and save
u2022 Now you are asked to Please maintain codes added in ALE entry methods, enter and choose XXXXXX and copy it. You should choose a FM similar to your one.
u2022 Enter your process code XXXX
u2022 Enter your function module XXXXXX
NOTE: The next 6 steps are used in workflow error handling.
u2022 Enter IDPKFIDCMT in object type
u2022 Enter MASSINPUTFINISHED in End event
u2022 Enter IDOCINVOIC in IDoc object type
u2022 Enter INPUTERROROCCURREDFI in IDoc start event
u2022 Enter INPUTFINISHEDFI in IDoc End event
u2022 Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object XXXXXXXX, 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.
Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
u2022 Add the message type XXXXX with process code XXXX.
u2022 Enter the output mode (background, immediately) for inbound processing and NO message code.
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.
You can find all the inbound and outbound processcodes in we64.
Regards,
SMS.

Message type, Idoc type and process code in ALE/Idoc

Each Idoc version(creams01 or cremas03) will have seperate process codes in Inbound process?
Whether Message type triggers the process code or the Idoctype/idoc triggers the process code in Inbound process?
regards
Message was edited by: henry

Hi Henry,
About your question as how should you assign seperate process code for the same message type ( with different IDoc Type )-
In We42, the message type can be assigned to the processing code. But here you will find that along with message type there are two more fields - Message Code & Message Function.
You can use any one these to serve your purpose.
e.g. you can assign
-process code P1 to message type M with Message code 1
-process code P2 to message type M with Message code 2
Further these process types can be configured to call separate FMs.
Now depending on IDOC types your external system should populate the message type as well as Message code so that accordingly process code will be determined at the time of inbound processing.
I hope it's clear & correct
Thanks,
Ram

EDI/ALE-Output type-Process code relation?

Hi.
In EDI preocessing the relation between the Message type and the process code is know.
But where is the realtion of either of these two to the output type?
When we hit a F4 in the message control in WE20 for process codes it gives us a list.
How is this linkages established.
Output type-process code-message type-output routines?
Please dont answer in vague terms.

Dear experts,
I am a little further now.
I used output condition WA01 which is already set up in NACE and in MN23 I set up:
In SP01 I can see the created Spool entries after creating the Good issue with ME2O. So the print out would work. But I need an EDI output....
I created a new output condition ZWA1 in NACE and set "Processing routines" to EDI.
I set "Partner functions" to EDI and LS - logical system.
In MN23 I have:
I set Event Type to "WA" because when I look at a material document in MB03 it also shows WA:
In WE20 I have my LS - logicals system and set up the output for MBGMCR03:
What confuses me is: I have to send the EDI output to a LS - logical system. But in MN23 I can't set the LS - it gives error: "You cannot enter a partner function for output ZWA1"
No IDoc is created so far - please help. Thank you.
Best regarsd,
Peter

PROCESS CODE IN INBOUND SIDE(ALE-IDOCs)

HI,
pls can you tell me procedure for creating PROCESS CODE IN
standalone method.

hi
create function module in se37
maintain charecterstics of that function module in tcode bd51
assign that function module to proceess code in using tcode we42
Reward for useful points
Regards
Nagesh.Paruchuri

Purpose of Process code

Hi what is purpose of Process Code
I know there we add Msg type and Function module what is its function that function module will helps in getting the data
and *what abt Msg type* and Process code there

Hi,
R/3 uses the method of logical process codes to detach the IDoc processing and the processing function module. They assign a logical name to the function instead of specifying the physical function name.
Logical pointer to a processing method
The IDoc functions are often used for a series of message type/IDoc type combination. It is necessary to replace the processing function by a different one. E.g. when you make a copy of a standard function to avoid modifying the standard.
Easily replacing the processing method
The combination message type/IDoc will determine the logical processing code, which itself points to a function. If the function changes, only the definition of the processing codes will be changed and the new function will be immediately effective for all IDocs associated with the process code.
For inbound processing codes you have to specify the method to use for the determination of the inbound function.
After defining the processing code you have to assign it to one or several logical message types. This declaration is used to validate, if a message can be handled by the receiving system.
The inbound processing code is assigned analogously. The processing code is a pointer to a function module which can handle the inbound request for the specified IDoc and message type.
The definition of the processing code is identifying the handler routine and assigning a serious of processing options.
Processing with ALE
You need to click "Processing with ALE", if your function can be used via the ALE engine. This is the option you would usually choose. It allows processing via the ALE scenarios.
Associate a function module with a process code
Table TBD51 to define if visible BTCI is allowed
For inbound processing you need to indicate whether the function will be capable of dialog processing. This is meant for those functions which process the inbound data via call transaction. Those functions can be replayed in visible batch input mode to check why the processing might have failed.
WE41 Process code outbound creation
WE42 Process code inbound
Regds
Sivaparvathi
Please reward points if helpful............

Error while creating inbound process code

Hi gurus,Iam creating a custom idoc.
800 -> sender
810 -> Receiver
i have completed outbound processing on 800.
On 810, completed following steps for inbound processing.
1.) I have added my Inbound FM in BD51.
2 ) Assigned my FM to Message type and Idoc type in WE57.
3 ) When adding my FM to process code in BD67, it is showing error that
Entry ZSATPC does not exist in TEDE2 - check your entry.
{ zsatpc is my custom process code }.
4) While Creating Process Code in WE42 with options [processing with ale service / Processing
by FM] and saving it is giving error that
" " is not a valid language.
And when I saw help (?) regarding this error, the following text appeared in a window.
Diagnosis
A key with language "" "" was specified for table "EDE2T". This is not a valid language.
This applies to field "LANGUA"
System Response
The system rejects the key.
Procedure
Enter a valid language. This is usually the language you logged on in.
You logged on in language "EN".
Table T002 contains a list of valid languages.
Please solve this error. Give me steps to create inbound process code.
thanx in advance. Hoping replies soon........
Satish.

Dear Satish,
Very peculiar. The language should come from your log on language. Try to login into the system again. Call we42 again and see if it works.
Regards, Rakesh

Need help in creating process codes

Hi All,
I need to create some message type and assign it to some idoc type , and i need to create process code and inbound function module for this.
Can some one please help me in this regard.
Thanks ,
Hem

hi
CATSDB CUSTOM IDOC TRANSFERMATION BETWEEN 2 DIFFERENT APPLICATION SERVERS
For this scenario Client 800 of application server SAPADM is the Sender and client 800 of application server SAP-REMOTE is the Receiver
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 CATSSENDER, ECC Logical Systems
o       Save and come back
o       Assign the CATSSENDER Logical System to client 800 of Application Server SAPADMAssign the ECC Logical System to client 800 of Application Server SAP-REMOTE
2. Creating the RFCs
o       Go to T. Code SM59
o       Expand R/3 Connections
o       Enter RFC Name as CATSSENDER
o       Connection Type as 3
o       Language as EN
o       Client as 800
o       User as SAPUSER
o       Password as YESV13
o       Target host as SAPADM
o       Click on Remote logon button to test the RFC
o       Enter RFC Name as ECC
o       Connection Type as 3
o       Language as EN
o       Client as 800
o       User as SAPUSER
o       Password as YESV123
o       Target host as SAPADM
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 ZCATSTIME and description
o       Save and back
4. Creating the Segment
o       Go to T. Code WE31
o       Give segment name as ZSEGMENTTIME
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 ZTIMEIDOC
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 backo       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 CATSSENDER
o       Select the model and click on Add Message Type Button
o       Give the Sender as CATSSENDER,
o       Receiver as ECC,
o       Message Type as ZCATSTIME
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 continueo
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 ECC (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 ECC
o       Double click on Message Type ZCATSTIME in Outbound parmtrs.
o       Check Receiver Port is assigned correctlyo
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 ZCATSTIME
o       Give Basic Type as ZTIMEIDOC
o       Release as 4.6C
o       Save and back10. Creating Inbound Function Module (Posting Program)
o       Go to T. Code SE37
o       Create a function Module ZCATSDB_TIMESHEET_SURESH
o       Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.
o       Import Parameters
          P_WORKDATE                    LIKE               CATSDB-WORKDATE
          P_COUNTER                        LIKE               CATSDB-COUNTER
          P_LSTAR                               LIKE               CATSDB-LSTAR
o       Export Parameters
o       Tables
             S_PERNR                      LIKE           ZCATSPERNR
[PERNR is select option parameters in ZCUSTOMIDOC report program so that it should be passed to function module ZCATSDB_TIMESHEET_SURESH in tables section. And also in tables section we used ZCATSPERNR, which is a global structure, which contains four fields as
Ø     SIGN
Ø     OPTION
Ø     LOW
Ø     HIGH]
o       Exceptions
o       Source Code
FUNCTION zcatsdb_timesheet_suresh.
""Local interface:
*" IMPORTING
*"     VALUE(P_WORKDATE) LIKE CATSDB-WORKDATE
*"     VALUE(P_COUNTER) LIKE CATSDB-COUNTER
*"     VALUE(P_LSTAR) LIKE CATSDB-LSTAR
*" TABLES
*"      S_PERNR STRUCTURE ZCATSPERNR
TABLES: catsdb, edidc, edidd. " using structures of catsdb, edidc, edidd
CONSTANTS: c_doctyp TYPE edidc-idoctp VALUE 'ZTIMEIDOC', " idoc type
             c_segnam TYPE edidd-segnam VALUE 'ZSEGMENTTIME',   "segment type
             c_mestyp TYPE edidc-mestyp VALUE 'ZCATSTIME'.   " message type
*001 comment begin
     creating internal tables with out header lines for catsdb, edidc, edidd and also
-           work areas
*001 comment end
DATA: it_edidc TYPE edidc OCCURS 0,    " control internal table with out header line
        it_edidd TYPE edidd OCCURS 0, " data internal table with out header line
        wa_catsdb TYPE it_catsdb1, " work area for it_catsdb internal table
        wa_edidc TYPE edidc, " work area for it_edidc internal table
        wa_edidd TYPE edidd, " work area for it_edidd internal table
        wa_zsegmenttime TYPE zsegmenttime, " work area for zsegment internal table
        v_occmax TYPE idocsyn-occmax,
        v_nbseg   TYPE i.
CLEAR wa_catsdb. " clears work area of catsdb
CLEAR wa_edidc. " clears edidc work area
*002 comment begin
Save the message type and the basic IDoc type in the control segment.
*002 comment end
MOVE c_mestyp TO wa_edidc-mestyp. " assigning custom message type to edidc workarea
MOVE c_doctyp TO wa_edidc-idoctp. " assigning custom idoc type to edidc workarea
*003 comment begin
Retrieve the maximum number of segments in the basic IDoc type.
*003 comment end
SELECT MIN( occmax ) FROM idocsyn INTO v_occmax WHERE idoctyp EQ c_doctyp AND segtyp EQ c_segnam.
*004 comment begin
Save the whole CATSDB table content in the IT_ZCATSDB internal table.
*004 comment end
SELECT pernr workdate lstar counter FROM catsdb INTO CORRESPONDING FIELDS OF TABLE it_catsdb WHERE pernr IN s_pernr AND workdate EQ p_workdate.
*005 comment begin
Create a data segment for each line of IT_ZCATSDB.
*005 comment end
IF sy-subrc EQ 0.
    LOOP AT it_catsdb INTO wa_catsdb WHERE pernr IN s_pernr.
      MOVE-CORRESPONDING wa_catsdb TO wa_zsegmenttime.
      CLEAR wa_edidd.
      MOVE c_segnam TO wa_edidd-segnam.
      MOVE wa_zsegmenttime TO wa_edidd-sdata.
      APPEND wa_edidd TO it_edidd.
      CLEAR wa_catsdb.
      CLEAR wa_zsegmenttime.
    ENDLOOP.
ELSE.
    MESSAGE 'NO DATA FOUND FOR GIVEN SELECTION' TYPE 'I'.
ENDIF.
*006 comment begin
Count the number of data segments.
*006 comment end
DESCRIBE TABLE it_edidd LINES v_nbseg.
*007 comment begin
If the number of data segments exceeds the maximum allowed number,then display an error message.
*007 comment end
IF v_nbseg GT v_occmax.
    MESSAGE 'IDOC ERROR Message' TYPE 'E000'.
ENDIF.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' " for creating an catsdb idoc
EXPORTING
master_idoc_control = wa_edidc
OBJ_TYPE = ''
CHNUM = ''
TABLES
communication_idoc_control = it_edidc
master_idoc_data = it_edidd
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.
ENDFUNCTION.
Save, check and activate
111. 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 ZCATSDB_TIMESHEET_SURESH Type as "F"
o       Basic Type as ZTIMEIDOC
o       Message Type as ZCATSTIME
o       Direction as 2
o       Save and back
Now Login in 800 client of Application Server SAP-REMOTE
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 ZCATSDB_TIMESHEET_SURESH
o       Give Input t. as 0 (zero)
o       Save and back13. Creating Process Code
o       Go to T. Code WE42
o       Click on Change, New Entries Button
o       Give Process Code name as ZCATSDB, 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 ZCATSTIME
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       Enter the short text and Technical name as CATSECC
o       Select the model view & click on Environment -> Generate Partner Profiles
o       Select Transfer IDOC Immediately and Trigger Immediately radio buttonso       Click on Execute 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 CATSSENDER
o       Double click on Message Type ZCATSTIME in Inbound parmtrs.
o       Give the Process Code as ZCATSDB
o       Click on Trigger Immediately Radio button
o       Save & Back
Save & Back
16. Creating the Selection Program (Outbound Program)
-         Login in client 800.
-         Go to T. Code SE38
-         Create a Report Program as ZCUSTOMIDOC with the following code
REPORT ZCUSTOMIDOC
       NO STANDARD PAGE HEADING.
TABLES:catsdb. " using structure of cats db table
*000 comment begin
     this selection screen contains one select option and one parameter
*000 comment end
SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS pernr FOR catsdb-pernr.
PARAMETER: workdate LIKE catsdb-workdate,
          LSTAR like catsdb-LSTAR,
          COUNTER like catsdb-counter.
SELECTION-SCREEN: END OF BLOCK b1 .
DATA: wa_val TYPE i.
wa_val = pernr-high - pernr-low.
*001 comment begin
      calling custom function module
*001 comment end
CALL FUNCTION 'ZCATSDB_TIMESHEET_SURESH'
EXPORTING
    p_workdate = workdate " passing workdate parameter
    p_LSTAR = LSTAR
    p_counter = counter
TABLES
    s_pernr    = pernr. " passing pernr select option
IF sy-subrc EQ 0.
MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' pernr-low ' AND ' pernr-high .
MESSAGE i000(zaluri) WITH   'IDOCS CREATED FOR EMPLOYEES BETWEEN' PERNR-LOW 'TO' PERNR-HIGH.
gives information message if idocs are created for given employees
ELSE.
MESSAGE e000(zaluri) WITH 'NO IDOCS CREATED FOR EMPLOYEES' pernr-low 'TO' pernr-high. " gives error message
" if idoc is not created
17. Transferring the CATSDB records from sender Application Server SAPADM to receiver Application Server SAP-REMOTE
-         Execute Report Program ZCUSTOMIDOC
-         Give the Range of PERSONNEL NO'S, Date, Activity Type, Counter to Transfer
-         Give Message Type as ZCATSTIME
-         Give Receiver Logical system as ECC
-         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
18. SENDING IDOCS FROM APPLICATION SERVER SAPADM
TO APPLICATION SERVER SAP-REMOTE USING WEDI
-         Go to T. Code WEDI & execute or T. Code WE19
-         Give idoc number it is generated recently
-         Continue & double click on segment to view data in segment
-         Click on EDIDC to give port, partner no, message type, partner
type of receiver. [For sender no need to give any port no leave it as
blank]
-         Click on Standard Outbound Processing button and click continue
-         You will get a message as idocs successfully transferred
Now Login in Receiver 800 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 CATSDB & press F7
-         See the contents of the table
-         The table is updated with the catsdb records transferred from 800 client with our selection program.
regards
Nagesh.Paruchuri

Error in Process code creation

Hi All,
I need to create a process code and i need to attach a custom function module for that process code.
So i have created custom FM.
afterward in WE42 ,
I gave custom process code name ,description and FM .
when i tried to save the same its giving following message.
For entry, access 'Function module for ALE-EDI inbound processing'
when i tried to give some entries its not accepting...
Please provide me the steps for process code creation.
Reg,
Hem.

hi
good
Definition
Another name for a specific process, for example function module or workflow. IDocs are read or written in this process.
Use
In the partner profiles, the processing is never addressed directly but rather always using a process code. You can therefore replace an old process with a new one for any number of partners by assigning the existing process code to the new process.
Two types of process code are used in conjunction with the partner profiles:
1) Outbound Process Code - if you are using outbound processing under Message Control, the IDoc is generated in the IDoc Interface. The process code names the relevant function module.
2)Inbound Process Code - names the function module or workflow which reads the IDoc data and transfers the data to the application document.
There are process codes for exception handling:
1) System Process Code - names the workflow which is triggered in inbound or outbound processing when an exception occurs.
2) Status Process Code - names the exception workflow which is triggered when an incorrect status is returned by the external system.
These two types are configured centrally and not on a partner-specific basis and therefore do not have to be maintained when a new process is defined. They were introduced for the sake of completeness, so that each process in the IDoc Interface is addressed using a process code.
reward point if helpful.
thanks
mrutyun^

Confusion on partner function of ALE process

Hi experts,
Now I am developing the ALE for message type ORDERS in inbounding process for testing purpose. Our customer is running their business in SAP and her company code is 6000 in her SAP system, and our company is vendor in her system, the vendor number is 1100. She create a purchase order and run the transaction code ME9F then the IDOC will send to our SAP system, and then the sales order is created in our system. Actually the whole process is OK. But I am really confused by the partner function setting and sales area setting in VOE4 and VOE2.
In VOE4, the setting is below:
Customer          Ext.Function         Name                            Exnternal partner          Int.no
6000                 SP                       Sold-to party                  6000                            6000
6000                 BP                       Bill-to party                    6000                            6000
6000                 PY                       Payer                            6000                            6000
6000                 SP                       Ship-to Party                  6000                            6000
In VOE2, the setting just like below:
Customer       Vendor number     Sorg.                   Dchl              Dv             Saty
6000              0000001100          1000                   12                 00              OR
We had to create a customer number 6000 in order to make the ALE process smoothly. So I just want to know:
1) We really need to make our customer number same as company code of customer in her SAP system if we use ALE ??
2) If answer of 1) is yes, then in our production system, the customer numbers are different from their company codes, what and how do you suggest to mapping the is relationship?? Use a user-exit in IDOC??
3) if answer of 1) is no, how can we make the ALE go next smothly??
Can any one give me a suggestion on above??? Thanks in advance.
Joe
Edited by: Joe.GR Chen on Jun 19, 2009 11:23 AM

hi,
to add partner function sales employee follow these steps:
1. img>S & D>basic functions>go to partner determination screen and select customer master and select your partner proceedure.
2. now double click on partners in partner proceedure and add partner function SE using new entries and save.
3. now assign the partner function to you account group and save
to create a sales employee goto t code PAL1 and create sales representative.
to add sales rep to your customer master goto your customer master using XD02 and in sales area tab goto partner tab and add the partner function SE and the sales rep number and save
regards,
krishna prasad

ALE Process code

Similar Messages

Maybe you are looking for