LOIPRO01: IDoc for Producation Order does processing affect stock, etc?

Hi Gurus,
we need to migrate some Producation Orders into our Target System. This have to be done via the IDoc LOIPRO01, which is for Production Order Master.
Now my question. What happens during the IDoc processing. Is only the Production Order created or will things like material consumption processed also?
I only need the Production Orders, the amount of the Material in stock and so on, should not be affected by the IDoc processing for LOIPRO01.
Thanks in Advance

Hi Udo
I believe that IDOC LOIPRO01 has only information about the Production Order
You can check the structure of this IDOC in this link
http://help.sap.com/saphelp_erp60_sp/helpdata/EN/1a/0e3601539911d1898b0000e8322d00/content.htm

Similar Messages

Generating an IDOC for each Order present in the file (File to IDOC)

Hi ,
I have a requirement where in i have to generate an idoc for each orders present in a file . Initially i had implemented 1:N mapping by changing the occurence of idoc to 1..unbounded & using it as external definition i was able to generate multiple idocs.
But now the requirement is that even if one record contains invalid data , then XI shoul process remaining records(which has valid data) & then raise an alert for the invalid record . I have implemented this approach by using BPM (splitting the message) & the sending out each record as a single message to (1:1 mapping between file & IDOC).
But now they dont want me to use an BPM . They want me to come up with an approach using 1:N mapping only where in i can make sure that the mappig doesnt fail even if there is one invalid record ,they want me to process remaining records & raise an alert for the invalid one .
As far as i know this cant be done without BPM . Please let me know any valuable suggestions or inputs if there is any
Regards
Vinay P.

Hi Vinay,
Had a similar requirement few days back..
What we did was to do a multimapping of 1:N where N = N1 and N2, N1 is the Idocs which you are doing today, N2 is the set of invalid records...
Now we have written this as a file and then created another interface which will pick the file and based on the name of file we decided the To address. We have used mail package and this interface (file to mail ) was made as a generic one so that it can be used across many interfaces...
filename and To address relationship was maintained as a value mapping in ID... You can have a thought of this approach and try to send the invalid records as a mail rather than alert.
Regards
Suraj

IDOC FOR PRODUCTION ORDER

Hi All,
Iam very new in using idocs, my requirement is to create a outbound idoc for production order (create/change) ,I got the Message type LOIPRO and idoc type LOIPRO01 there is no process code so i created a Z process code with FM (CLOI_MASTERIDOC_CREATE_LOIPRO) . Please explain how to proceed further in NACE etc
Thanks in advance,
Pria.

I have message type LOIPRO.
I am using that to trigger Production Order IDOCS.
I'm using the following fields below. My question: What Object/Table/Field combination do I use to track when STATUS has changed?
ORDER     AFKO     AUFNR
ORDER     AFKO     GAMNG
ORDER     AFKO     GLTRI
ORDER     AFKO     GLTRS
ORDER     AFKO     GSTRI
ORDER     AFKO     GSTRS
ORDER     AFKO     KEY
ORDER     AFKO     PLNBEZ
ORDER     AFVC     LTXA1
ORDER     AFVV     BMSCH

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Generating idoc for Purchase orders - ORDERS05

Hi,
Can you please let me know how to generate idoc for Purchase orders - ORDERS05-manually, not by activating change pointers.

hi
i believe u wont have this functionality as it is a transcational data and the one way of doing it by configuring output types only.

I found a exit CIFPUR02 for purchase order inbound process.is it suitable?

I found a exit CIFPUR02 for purchase order inbound process.is it suitable?
my idoc is PORDCR102 AND message type is PORDCR1. my requirement is this is EXIT should trigger before saving the data in me21n.
Edited by: rk.kolisetty on Jun 24, 2010 4:59 PM

Hi,
Following are the user exit relevant to T Code ME21n.
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMEKO001 Extend communications structure KOMK for pricing
LMEKO002 Extend communications structure KOMP for pricing
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Rgd,
Chetan

Creating an IDOC for purchase order

Hello gurus,
I want to generate an IDOC for purchase order.
The Logical System, RFC connection, ports definition is already defined.
In my system i have 800 client as source/sender and 100 client as target/reciever.
On Outbound side-> In Partner profile
I defined-
1. Partner No.- devclnt100
2.Type- US (User)
3. Agent - SAPUSER
In Outbound parameters-
I created message type as Orders.
One thing to note that my partner system is LS i.e. Logical System
Then in Outbound Options-
I mentioned Reciver Port - 800Port
Output Mode- I selected "Transfer Idocs immediately"
& "Do not start subsystem"
In Idoc type-
I gave following information-
Basic Type - Orders05
In Message Control tab i mentioned-
Application - EF
Message Type - NEU
Process Code - ME10
In NACE Transaction Code-
I selected EF Purchase Order as my condition for output control
In that- In output types-
I selecte NEU and double clicked. I checked whether Access to Conditions check box is checked and multiple issuing is checked.
In Dialog structure-Processing routines I checked that -
For Output type - NEU
Application - EF
Processing routines are defined-
medium-Distribution ALE
Program -RSNASTED
Form Routine - ALE_PROCESSING
I think these are the very basic settings that need to be done for creation of Idoc.
Now when i create a PO and then SAVE it an IDOC must be generated.
But when i go to transaction Code WE02. It shows me message "No Idocs genereated".
What is the problem? Where am i going wrong?

Hi Yayati,
Here are all the settings that you need to do. I am not sure which all settings are present so kindly confirm.
Sending side Client800:
1. WE20 - under LS - Outbound parameters - message type = Orders , basic type = Orders05
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
3. NACE - App = EF - Output Types - Processing Routines - Add medium = A (Distribution (ALE)) , Program = RSNASTED, Routine = ALE_PROCESSING.
4. NACE - App = EF - Output Types - Partner Functions - Add medium = Distribution (ALE), Funct = VN.
5. Name - App = EF - Condition Records - Output type = NEU , Choose ur combination (Mine is DocType/Purc Grp)
Pur.Doc Type = NB (Execute) , Add row Medium = A ,Function = VN and other details u choose.
Receiving side Client100:
1. WE20 - under LS - Inbound parameters - message type : Orders ; Process Code : ORDE
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
For the PO which you have created, go to the PO in ME23N, click on messages .
There should be a line : Output = NEU, Medium = Distribution (ALE)... etc.
If its present then the configuration was correct.
If it has a yellow triangle means it was not processed.
Regards,
Jovito.
Edited by: dsouzajovito on Dec 30, 2010 10:24 AM

Business Object (BAPI/IDOC) for production Order

Hi All
I have requirement where data is coming from legacy system to R/3 via XI to generate a production order. I am not able to get right BAPI/ IDOC for inbound Production Order. Can anyone has done similar scenario. Can u suggest me BAPI or IDOC for same. I am using IS-Mills 4.7 version for R/3
Thanx in advance
Regards
Vinod

HI Vinod,
I think U can use IDOC <b>LOIPRO01</b> for Production Order...
Regards,
Sridhar Reddy

Add segment to outbound Idoc for Sales order

HI experts,
I need to add segment E1EDP02 under Existing segment E1EDP01 for outbound IDOC for Sales order. FM" IDOC_OUTPUT_ORDRSP".
I have used the Exit : "EXIT_SAPLVEDC_003" for the FM "IDOC_OUTPUT_ORDRSP" in the include of the Exit i wrote my code also for adding segment and activate it.
But when i am trying to debug the code it's not working
So please guide me how to debug it
I have followed below steps to Debug.
1. In VA02 i have repeat the output.
2. Put the breakpoint in the Exit include program .
3. put the Breakpoint in ALE processing Routine in RSNASTED program also
4. Trigger the program RSNAST00 by giving the Parameter value of SALES ORDER number and execute.
But not working
And i need to know whether i have used the Correct EXIT or not.In that case how to identify the correct exit's
Thanks In advance

Hi,
I hope you have to add your segments through WE30 first for your IDOC type.
Cheers,
Raja.D

Urgent: Creating ALE IDOC for SALES ORDER

hi
please tell me <b>step by step procedure to create ALE IDOC for SALES ORDER?</b>
reward for sure
regards
ravish

Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards

Standard Idoc for Work order?

Hi,
Can you please let me know what is the Standard Idoc for Work order?
Thanks
POINTS WILL BE AWARDED

Hello,
Standard IDOC type for Work Order is LOIPRO01.
Thanks,
Venu

How to find the standard Idoc for Transfer Order (LT03)

hi
How to find the standard Idoc for Transfer Order (LT03)
How to create the Idoc on LT03
plz help me out
Thank u
Ram

Someone is using FM: L_IDOC_INPUT_WMTORD, message type WMTORD and basic type WMTOID01 in doing this when trying to send an Idoc to an external system when a transfer order for a delivery note is created (LT03). Is it OK
Please reward points

Send Idoc For Purchse Order

Hi Friends,
I have Configure All the things require to send idoc for purchse order..........when i m creating purchase order from source system
it's getting send to traget system....................
but in target system giving error in idoc.that
VKORG, VTWEG, SPART cannot be determined for customer S004 , vendor 0006000023
i m using message type....ORDERS............
can antbody pls tell me how to maintain VKORG, VTWEG, SPART
in oreders message type.......there no fields in this message type.......i have checked it through se19...............

Hi ,
I have same problem ,
How to send IDOC of Purchase Order to URL of our vendor.
The Idoc is created , but how to send it to the web?
Anyone knows?
Thanks
Edited by: Moshe Stein on Feb 28, 2008 11:08 AM

If the little slide volume button is down for no sound does it affect the video being recoreded with audio?

I recoreded videos on my iphone 4 from a concert and i just now realised the slide button on the side was down for no sound, does that affect the audio in the recording?

No. Play the video and see.

IDOC for Sales order

Dear Guru's,
could anybody help me in creating the IDOC for sales order.
As per My client Business Requirment we require the following Fields in One Basic Type only.
The Fields are as follows.
Order Type,Sales Area,Sales Office,Sales Group,Material Number,Order Quantity,Purchase order Number,Purchase order Date,
Sold to party,Ship to party,Bill to party,Payer,
Vendor no ( It is Third Party order)
Contract Start Date, Contract End Date (in order we will give these dates for periodic billing purpose )..
Now i want all the fields will include in one single Basic Type.
Thank you
suribabu

hi,
please check this link:
this might be help ful.
http://wwwdotsaptechnicaldotcom/Tutorials/ALE/Guide/Index.htm
balajia

LOIPRO01: IDoc for Producation Order does processing affect stock, etc?

Similar Messages

Maybe you are looking for