Parameters for IDOC CLFMAS01
Hi All
I am trying to test the IDOC CLFMAS02 but do not know the parameters that needs to be passed.
Kindly let me know what are the parameters that needs to be passed to different segments.
Below are the segments that are present
E1OCLFM
E1KSSKM
E1AUSPM
E1DATEM
E1UPSLINK
Thanks in advance
Regards
E1OCLFM-MSGFN =
003 Delete: Message contains objects to be deleted
004 Change: Message contains changes
005 Replace: This message replaces previous messages
009 Original: First message for process
023 Wait/Adjust: Data should not be imported
018 Resend
E1OCLFM-OBJEK = AUSP-OBJEK
E1OCLFM-KLART = AUSP-KLART
E1OCLFM-MAFID = AUSP-MAFID
E1KSSKM-CLASS = KLAH-CLASS
E1KSSKM-STATU = KLAH-STATU
E1AUSPM = AUSP table data
E1DATEM = date details
E1UPSLINK = "I didn't use it"
Similar Messages
-
Parameters for IDOCs - Incoming Invoices
Hi All,
We are able to post Incoming Vendor Invoices(T. code : MIRO) thru IDOCs. We would like to extend the functionality for Credit memos in Logistics Invoice Verification (LIV) as well.
Request you to provide us the changes/parameters, which we would need to make to achieve desired functionality
Thanks & Regards,
AnjiHi Anji,
Would you pls give the idoc names for Invoice posting & Credit memo postings.
Regards
Basavaraj Patil -
Function module creation for IDOC processing...
hi Experts,
i want to create a function module for idoc processing..
message type: zashpmnt
idoc type : shpmnt05
plz tell me which standard FM is used... and tell me what changes i want to do in it....
Tnx in Advance..Hello,
If you are trying to process an Outbound IDoc for the SHIPMNT05 IDoc Type with an Extension, you can use the IDOC_OUTPUT_SHPMNT Function Module which is assigned to SHPM Process Code.
In Addition, since you have an IDoc Extension, you are required to populate the Custom Segment / Fields. For this, there is a Customer Function / Exit called EXIT_SAPLV56K_002 which you can use it for adding your Custom Segments to the IDoc ZSHPMNT05.
If you are writing code in this exit, make sure to create a Project in CMOD.
Also, ensure that you've made the assignment in WE82 with the Message Type , IDoc Type & the Extension.
For Inbound, if you would like to Create a Custom Function Module, you can follow the Naming Convention Z_IDOC_INPUT_SHPMNT for which you are required follow the below Steps.
1. Register the FM as Inbound FM in BD51 T-Code.
2. Assign the FM to IDoc Type & Extension in WE57.
3. You'll need to Create a Custom Process Code in WE42 in which you are required to make add your FM.
4. Maintain Partner Profiles in WE20.
5. Have the Process Code Migrated to the Testing Environment as creation of Custom Process Code is a Customizing Activity and it requires a Customizing Request to be created / Migrated.
6. Define the Parameters as defined in the Standard Inbound Function Modules such as IDOC_INPUT_ORDERS , IDOC_INPUT_DELVRY etc.
Thanks and Regards,
Venkat Phani Prasad K -
Pls send material for idocs in ECC 6.0
Pls send material for idocs in ECC6.0
Hi sitaram s ,
IDoc
- IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful -
Process code for Idoc BANK_CREATE01 and BANK_CHANGE01
hi,
I want to create partner profile for Idoc BANK_CREATE01 and BANK_CHANGE01 standard Idocs.
But in transaction we64 , i am not finding the inbound process code for it.
So di i have to create a process code for it??
If yes , how do i create it and also the function module to be created.
kindly help.
Regards,
Loveenahi ,
To create a partner profile <b>Tcode WE20.</b>
for your inbound or outbound idocs , just add these idocs in outbound or inbound parameters . For Idoc to File or File to Idoc , it is sufficient.
before creating partner profile you have <b>to create port Tcode WE21</b>
hope this will help
regards
HONEY -
Hi am interested to learn about idocs can you provide me some useful links
Hi saranya srithar ,
IDoc is an Intermediate document that holds application data.
A container used to exchange data
It is independent of the complex SAP structure to store data.
It serves as the vehicle for data transfer.
IDoc Type defines the structure and format in which the data is exchanged.
It is similar to a structure in SAP
IDoc data is an instance of IDoc Type
IDoc acts as a standard SAP interface to exchange business data through ALE.
From an SAP system, an IDoc can be sent to and received from
An SAP R/3 system
An SAP R/2 system
An EDI subsystem
Any third-party application software
Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
These r all the t/codes which we will come across in IDocs:
TCODE TTEXT
BD10 Send Material
BD100 IDoc display object channel view
BD101 Consistency check
BD102 Outbound registry
BD103 Inbound registry
BD104 maintain tbd53
BD105 Maintain Supported Business Objects
BD11 Get Material
BD12 Send customer
BD13 Get customer
BD14 Send vendor
BD15 Open vendor
BD16 Send Cost Center
BD17 Get Cost Center
BD18 Send General Ledger Account
BD19 Get General Ledger Account
BD20 IDoc passed to application
BD21 Select change pointer
BD22 Delete change pointers
BD23 Delete serialization data
BD24 Send Cost Elements
BD25 Send Activity Type
BD26 Get Activity Type
BD27 Send cost center activity prices
BD28 Send obj/cost element control data
BD30 Distribute material object list
BD31 Distribute document object list
BD32 Distribute plant allocations(matBOM)
BD33 Distribute material variants (ALE)
BD34 Distribute order BOM
BD35 Send Business Process Groups
BD36 Send Business Processes
BD37 Send Business Process Price
BD40 Read change pointer for group
BD41 Dispatch IDocs for group
BD42 Check IDocs for group
BD43 Post IDocs for group
BD44 Assign Message Types to Serlz. Group
BD47 Dependencies between methods
BD48 Dependency method - message
BD50 Activate Change Ptrs for Mess. Type
BD51 Maintain function modules (inbound)
BD52 Activ.change pointer per chng.doc.it
BD53 Reduction of Message Types
BD54 Maintaining Logical Systems
BD55 Maintain IDoc Conversion
BD55OLD Maintain IDoc Conversion
BD56 Maintain IDoc Segment Filters
BD57 Maintain link and serialization ty.
BD58 Convert organizational units
BD59 Allocation object type -> IDoc type
BD60 Additional data for message type
BD61 Activate Change Pointers - Generally
BD62 Define Segment Conversion Rule
BD62OLD Define Segment Conversion Rule
BD63 Transport ALE Tables of Message Type
BD64 Maintenance of Distribution Model
BD65 Maintain IDoc type required fields
BD66 IDoc type field -> change doc.field
BD67 Maintain methods (inbound)
BD68 Maintain Lists
BD68OLD Maintain Lists
BD69 Assignment of Message Type to IDoc
BD70 Synchronize Number Ranges
BD71 Define FM for dependent bus. object
BD72 Activate Events
BD73 Reposting of IDocs (ALE)
BD75 Convert IDoc Status
BD77 Distribution of control data
BD78 Monitoring control data distribution
BD79 Maintain IDoc Conversion Rules
BD79OLD Maintain IDoc Conversion Rules
BD81 Filter objects parameter filtering
BD82 Generate Partner Profiles
BD83 Send IDocs after an ALE error
BD84 Post IDocs after ALE error
BD85 Consistency check for transfer
BD86 Consistency check for sales
BD87 Status Monitor for ALE Messages
BD89 Control data model. - initial screen
BD91 Send Characteristic
BD92 Send Class
BD93 Send Classification
BD95 Specify ALE object types
BD96 filter objects of receiver determin.
BD97 Assign RFC dest. to Logical Systems
BD98 Consistency Check Workflow Connectn.
BD99 Message type dependencies
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDocs by Content
WE10 Search for IDoc in Archive
WE11 Delete IDocs
WE12 Test Modified Inbound File
WE14 Test Outbound Processing
WE15 Test Outbound Processing from MC
WE16 Test Inbound File
WE17 Test Status File
WE18 Generate Status File
WE19 Test tool
WE20 Partner Profiles
WE21 Port definition
WE23 Verification of IDoc processing
WE24 DefaultValuesForOutboundParameters
WE27 DefaultValues for Inbound Parameters
WE30 IDoc Type Development
WE31 Development IDoc Segment
WE32 Development IDoc View
WE34 Object for Display of XML IDocs
WE40 IDoc Administration
WE41 Process codes, outbound
WE42 Process codes, inbound
WE43 Funct.module: Status record display
WE44 Partner Types and Checks
WE45 Forward (inbound) (V3, EDILOGADR)
WE46 Error and Status Processing
WE47 Status Maintenance
WE50 System process codes: Texts
WE51 System process codes: Change texts
WE54 FMs for changing file names
WE55 Function Module for Path Names
WE56 IDoc Administration
WE57 Assignment Messages for Appl. Objs
WE58 Status process codes: Texts
WE59 Change status process codes
WE60 Documentation for IDoc types
WE61 Documentation for IDoc record types
WE62 Documentation for segments
WE63 Documentation
WE64 Documentation message types
WE70 Conversion: Basic types
WE71 Conversion: Extensions
WE72 Conversion: IDoc types
WE73 Conversion: Logical messages
WE81 Logical message types
WE82 Assign Messages for IDoc Type
WE84 Assignment of IDoc and appl. fields
WE85 Create Rule Names
WEBU Printing Labels via Assortment List
WEDI EDI Basis
WEINBQUEUE IDoc Inbound Queue
WEKF Purchase order SAP Retail
WEL0 Forward (inbound) (EDILOGADR)
WEL1 EDI: Interface Invoice for EDILOGADR
WELI Maintain Status Groups
cheers!
gyanaraj -
hi gurus,
send me the sample coding
i need a zprogram for idoc using master_idoc_distribute
please send me any sample programHi,
DATA: Begin of imara occurs 0,
matnr like mara-matnr,
mtart like mara-mtart,
mbrsh like mara-mbrsh,
meins(3) type c,
end of imara.
data: begin of imakt occurs 0,
maktx like makt-maktx,
end of imakt.
DATA: wamas_con LIKE edidc,
imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,
icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.
PARAMETERS: e_matnr LIKE mara-matnr,
e_msgtyp LIKE edidc-mestyp,
e_rcvprn LIKE edidc-rcvprn.
retrive app. data from DB
SELECT matnr mtart mbrsh meins FROM mara INTO TABLE imara WHERE
matnr = e_matnr.
SELECT maktx FROM makt INTO TABLE imakt WHERE
matnr = e_matnr.
*Master idoc control record
wamas_con-rcvprt = 'LS'.
wamas_con-rcvprn = e_rcvprn.
wamas_con-idoctp = 'YMATMAS1'.
wamas_con-mestyp = e_msgtyp.
master idoc data records
LOOP AT imara.
imas_data-segnam = 'Y1MARA'.
move imara to imas_data-sdata .
APPEND imas_data.
ENDLOOP.
LOOP AT imakt.
imas_data-segnam = 'Y1MAKT'.
imas_data-sdata = imakt.
APPEND imas_data.
ENDLOOP.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
master_idoc_control = wamas_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.
Regards,
Priyanka. -
Determination of QOS for IDOC messages
Hi,
sending IDOC from SAP to XI, and then to an external system using a JDBC adapter, the QOS for messages is automatically set to EO: anyone knows if it's possible to change this parameter (I need EOIO)? Where can I find documentation about setting/changing QOS?
Thanks for any suggestion.
SimonaI had the same scenario as Simona and at the end it turned out to be pretty simple (if WAS >= 6.40). On the sender system (SAP ERP) in partner profiles -> in the outbound parameters for the message type, you need to check Queue Processing parameter. When you do this an aditionalfield will apear: Rule name. This determines which rule will be used as QueueID. Rules are customized in WE85 where you can assign your own function modules to custom rule names.
Once I assigned appropriate rule (for test I used FIRST_16_OF_MESTYP) xml message was automaticaly set to
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
and the message got the QueueID XBQO* (in SXMB_ADMIN).
Again, if WAS is WAS >= 6.40 you don't need to set up IDXQUEUE table.
Regards,
Elvis -
RFC Destination type for IDOC to FILE
Hi,
wat is the RFC Destination type for IDOC to FILE ?
jeffhi,
u shud create rfc dest tye: R/3 connections...that is type 3.
refer this:
R/3 side settings
1. SM 59 (RFC destinations)
Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Give the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
XI side settings.
1. SM59 (RFC destination)
Configure the RFC destination pointing to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
[reward if helpful]
regards,
latika. -
Hi,
For configuration of IDOC adapter
1) we need to create RFC Desination both XI System and R3 System.For port creation if v given same port name in both XI system and R3 system it will work or not ?
2) On Receiver SAP system, we need to configure the logical system normally for XI system, were v can find logical system of XI System.
3) Can RFC Destination b same on both systems( R3 system, XI System)
Regards,
PraveenHi
The following configurations are needed for Idoc scenarios
1) ECC Configuration : a) Create RFC connections from ECC to XI in SM59. rfc connection name should be target XI logical system name . BD54 or SALE are the tcodes for checking the logical system for respective client.
b) Create port in we21 & provide the above RFC destination.
c) Now Create Partner Profile in we20 ...partner profile name should be target logical system name.
assign the outbound parameters with receiver port created in we21.
2) XI Configuration : a) Create a RFC connection for XI to ECC ...rfc name should be target logical system name(ecc).
b) Create port in IDX1...it should be SAPXXX..where XXX is the ecc system id.
c) Import the idoc metadata in IDX2.
For Outbound idocs generate the model view in BD64.
Regards
Abhijit -
What are the parameters for DB2 / JDBC Connetivity?
I have insert IDoc data from SAP > XI > DB2.
What are the connection parameters for the Reeiver JDBC channel to connect from XI to a DB2 database?
Regards,
BhaskarHey
please have a look at the following thread
JDBC connection to DB2 Database
also please search SDN for DB2 drivers,there is lots of material for it
thanx
Aamir -
Control parameters for data transfer
Hi!
There are no data in SBIW source system - General Settings - Maintain Control Parameters for Data Transfer.
How does it have an influence on loading data?Hi,
Maximum size of a data packet in kilo bytes
The individual records are sent in packages of varying sizes in the data transfer to the Business Information Warehouse. Using these parameters you determine the maximum size of such a package and therefore how much of the main memory may be used for the creation of the data package. SAP recommends a data package size between 10 and 50 MB.
Frequency with which status Idocs are sent
With this frequency you establish how many data IDocs should be sent in an Info IDoc.
Standard settings
Frequency 1 means, for example, that there is an Info IDoc for every data IDoc. In general, you should choose a frequency between 5 and 10 but not greater than 20.
Recommendation
The larger the packet size for a data IDoc, the smaller you should set the frequency. By doing this, you make it possible to get information on the respective data load status in relatively short time periods when uploading data.
Maximum number of parallel processes for data transfer
Select a number greater than 0.
Parallel processes can be set from the SAP core release 3.1I onwards.
These parameters are, therefore, ignored in releases before 3.1I.
However, there is a possibility of importing the SAP release 3.1I into earlier releases.
The more parallel processes that can run the better the performance of your system will be. However, you must bear in mind the number of available dialog processes here.
It will be fine and more effective if you use sap recomended values in those respective fields -
Distibution Model- Outbound parameters for message type could not be found
Hi SRM Gurus,
Have you ever encountered this error while buidling Distribution model in BD64 -
When I try to generate partner profile, I am getting this error-
Outbound parameters for message type BBPCO BBPCO01 could not be created
Partner not found in partner table
This error is occuring for all message types.
Please let me know the solution if anyone has encountered this error before.
Thanks & Regards
KapilHi
Are you geting this error while generate partner profile?
hope your sender and receiver logical system are correct.double check.
VERSION 3
OUTPUT MODE - tRANSFER idoc immediately option
connectivity between both sytems are ok.
did you save modelview ?
now ports automatically created . check we21 ,we20..
check your sm59 rfc destination? what type connection you made ? hope you maynot do mistake. howevercheck itup.
ask basis consultant assistance why ports anot genrated for backend system after you executed
tbd05 - do yo have entry ?
regards
muthu -
Steps for Idoc to EDI Subsystem
Hi all,
Can anyone tell me the steps that i have to worry about to send an idoc immediately to EDI Subsystem
I mean what all things i have to specify while creating ports and partner profiles etc
ThanksSending Order Confirmations by EDI (SD-SLS)
Use
By setting up and using the Electronic Data Interchange functions in the R/3 System, you eliminate the need to print documents and send them through the standard mail system. Instead, you send the information electronically. This method is more practical, convenient, and allows you and your customer to process data faster.
In this EDI scenario, you process and send order confirmations to a customer's R/3 Purchasing system.
Prerequisites
Application
Customizing
To process outbound order confirmations, you need to make all of the necessary EDI settings in Customizing for Basis. You make settings for output control in Customizing for Sales and Distribution.
Output Control
The standard SD condition components are:
Condition component Value
Sales document type AA
Output determination procedure V10000
Condition type BA00
Transmission medium 6 (EDI)
Access sequence 0001
Processing subroutine Program RSNASTED, form routine EDI_PROCESSING
Partner function SP (sold-to party)
Application V1
Condition records for outbound order confirmations are maintained in Customizing for Sales and Distribution. Choose Basic Functions Output Control Output Determination Output Determination Using the Condition Technique Maintain Output Determination for Sales Documents.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data for the outbound parameters for partner profiles and the additional profiles for message control:
Field Value
Message type ORDRSP
Partner type KU (customer)
Partner function SP (sold-to party)
Receiver port e.g. SUBSYSTEM
Output mode e.g. Transfer IDoc immediately
Basic type ORDERS04
Process code SD10
Activities
Create an order. When you save the document, the system uses your settings in output control to find the appropriate condition record and send confirmation of the order by EDI. To review and maintain output data in the document, choose Extras Output Header.
Receiving Acknowledgments via EDI (MM-PUR-GF-CON)
Use
You have arranged with your vendor that that latter is to send you acknowledgments in respect of purchase orders or outline agreements received from your company. (Note: both kinds of acknowledgment are generally referred to as "order acknowledgments" in the system. The corresponding EDIFACT term is "order response" (ORDRSP).)
You have the option of working exclusively with acknowledgments. The acknowledgment is then purely informative in nature, since only the acknowledgment number is recorded in the system.
If you wish to receive different kinds of vendor confirmation, such as both order acknowledgments and shipping notifications (also known as advance shipping notices - ASNs), it is possible for quantities and dates to be entered in the system automatically).
For more information on this topic, refer to the MM Purchasing documentation ( Confirmations from the Purchasing Viewpoint and Receiving Confirmations via EDI).
Prerequisites
Application
To work with several categories of vendor confirmation, you must:
u2022 Enter a confirmation control key on the item detail screen
u2022 Set up the confirmation control facility in Customizing for Purchasing (Purchasing Confirmations Set up Confirmation Control). There you can specify the order in which you expect confirmations from your vendors, for example.
Under Confirmation sequence, you can:
u2022 Specify tolerances for date and price checks
u2022 Allow vendor material changes (VMat indicator)
u2022 Adopt vendor price changes (Price indicator)
Do not use a confirmation control key if you work exclusively with acknowledgments.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing Messages EDI Set up Partner Profile):
Parameters for Inbound Messages
Field Value
Partner type LI
Partner role LF
Message category ORDRSP
Process code ORDR
Processing Initiate immediately or process via background program
Activities
When an acknowledgment is received in the form of an incoming EDI message, the system checks whether a confirmation control key has been entered in the relevant PO or outline purchase agreement.
u2022 If there is no confirmation control key, only the acknowledgment number is entered on the item detail screen.
u2022 If there is a confirmation control key, the system updates the confirmation overview. That is to say, the dates and quantities set out in the acknowledgment that has just been received are recorded and taken into account in the overview. To view acknowledgments that have been received, choose Item Confirmations Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI. The system also enters the IDoc number in the External document column.
An IDoc can always acknowledge one purchase order only. The acknowledgment relates to the PO item, not to any individual schedule lines.
Exceptions
When an acknowledgment is received via EDI, the system automatically checks quantities, prices, and dates. In checking quantities, it applies the over- and underdelivery tolerances set for the item. You can set tolerances for prices and delivery dates in Customizing for Purchasing under Set up Confirmation Control.
The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
For more information on this topic, refer to the section Error Correction (Receiving Confirmations via EDI) of the MM Purchasing documentation.
Sending PO Change Notices via EDI (MM-PUR-PO)
Use
This section describes how to transmit a change notice relating to a purchase order that has already been sent to a vendor.
The function corresponds to the transmission of a purchase order via EDI.
Prerequisites
Application
You have already successfully transmitted the original purchase order to the vendor via EDI.
Message Control
You have created message condition records for your EDI vendors (Purchasing Master data Messages Purchase order Create).
Use the message type NEU to transmit PO change notices.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing Messages Set up Partner Profile):
Parameters for Outbound Messages
Field Value
Application EF ( Purchasing: purchase order)
Message category ORDCHG
IDoc type ORDERS02 or ORDERS04
Process code ME 11 (ORDCHG: PO change notice)
If you wish to transmit PO conditions or texts to your vendor, you must create an IDoc view. For more information on this topic, see Sending a Purchase Order via EDI.
Activities
Change an existing purchase order via Purchasing Purchase order Change. Make the necessary changes and save the PO.
The new message is compared with the last successfully transmitted message. PO change notices indicate whether any new items have been added to the PO, and/or whether any already transmitted items have been changed.
When the message is transmitted, only those changes that are simultaneously new and print-relevant are included. The system sets the change indicator for the new message. To check the change indicator, choose Header Messages in the PO item overview.
See also:
MM Purchasing: Creating a Purchase Order
Cross-Application Components: Customizing Message Control in Purchasing (MM): Example: Purchase Order
Receiving Order Changes by EDI (SD-SLS)
Use
In this EDI scenario, you receive and process order changes sent by a customer from an R/3 Purchasing system.
Prerequisites
Application
General
You can receive and process order changes in your system only on the basis of an existing order.
Customizing
To process incoming order changes, you need to make all of the necessary settings in Customizing for Basis. There are no special settings for Sales and Distribution.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:
Parameter Value
Partner type KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!
Message type ORDCHG
Process code ORDC
Processing Process immediately
Allowed Agents Enter an R/3 user or an organizational unit, for example.
Activities
Inbound Processing
The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_ORDCHG in Sales and Distribution. The ALE services are called.
The system processes the IDoc in the background, using the data records in the IDoc to determine the relevant order.
If processing is successful, the system updates the sales order. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.
Exception Handling
If it cannot determine an order, or if an error occurs in processing, the system determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.
To display an IDoc for order changes, choose Environment Display facsimiles in the order. The system displays a dialog box of object links where you can choose Linked IDocs. -
We 19 rest tool for idoc processing
hi to all abap gurus
i heard that we19 is test tool for idoc proceesing and it is also also used for idoc deletion .
may i know what is idoc testing why it is required . can u pls explain n in detail ?
and so many options are there in we19 tcode like inbound function module .
and tell me how to create idoc dynamically and send to the other system by using we 19 tool
thanksssss in adavanceIntermediate Document
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data. IDoc is not a process.
- IDocs are stored in the database.
- In the SAP system, IDocs are stored in database tables.
- IDocs are independent of the sending and receiving systems.
- IDocs are independent of the direction of data exchange.
Creation of IDOCs
? Transaction code: WE 30
Defining Segment:
Creating Segment : Tcode - WE31
Creating Message Type : Tcode - we81
Assigning Message type to Idoc type: Tcode - we82
Process
The two processes for IDoc are Outbound Process and Inbound Process.
Outbound Process
When the data is sent out from the system, the process is called Outbound Process and the IDoc is known as Outbound IDoc.
Inbound Process
When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.
Outbound Process (Sending System) Steps :
1) Goto Tcode SALE:
Click on Sending & Receiving Systems à Select Logical Systems
Here Define the Logical Systems à Click on Execute Button
Go for New Entries
1) System Name : LOG1
Description: Sending System
2) System Name : LOG2
Description: Receiving System
Press Enter & Save it will ask for Request if you want new request create new request or press continue for transferring the objects.
Assigning Client to the Logical System:
Select Assign Client to Logical Systems -à Execute
Ø 100 à Double click on this and give the following information
Client : Sending System
City : Chennai
Logical System : LOG1
Currency :
Client role :
Ø 250 à Double click on this and give the following information
Client : Receiving System
City :
Logical System : LOG2
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 : LOG2
Connection type : 3
Target Host : sappdc.wipro.com
System No : 00
Client : 210
User : Login user name
Password :
Save this & Test it and Remote Login
Step 3) Goto Tcode BD64: - Click on the change button
Click on the create model view
Short Text: model view
Technical Name: LMOD
Save this & press ok
Select just created model view
Name: "LMOD"
Goto add message type
Model Name : LMOD
Sender : LOG1
Receiver : LOG2
Message type: ZAZHARMESS
Save and press Enter.
4) Goto Tcode BD82:
Give Model View : LMOD
Partner system : LOG2
Execute this by pressing F8
It will gives you sending system port No: A00000000089 (Like)
5) Goto Tcode BD64:
Select the model view
Goto à Edit à model view à Distribute
Press ok & Press Enter.
Run your Zprogram
REPORT ZIDOC1 .
DATA: Begin of imara occurs 0,
matnr like mara-matnr,
mtart like mara-mtart,
end of imara.
DATA: wamas_con LIKE edidc,
imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,
icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.
PARAMETERS: e_matnr LIKE mara-matnr,
e_msgtyp LIKE edidc-mestyp,
e_rcvprn LIKE edidc-rcvprn.
retrive app. data from DB
SELECT matnr mtart FROM mara INTO TABLE imara WHERE
matnr = e_matnr.
*Master idoc control record
wamas_con-rcvprt = 'LS'.
wamas_con-rcvprn = e_rcvprn.
wamas_con-idoctp = 'ZAZHARIDOC'.
wamas_con-mestyp = e_msgtyp.
master idoc data records
LOOP AT imara.
imas_data-segnam = 'ZAZHARSEG'.
move imara to imas_data-sdata .
APPEND imas_data.
ENDLOOP.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
master_idoc_control = wamas_con
TABLES
communication_idoc_control = icom_con
master_idoc_data = imas_data
COMMIT WORK.
6) Verifying Transfer of IDOCs Tcode - we05
ALE/IDOC Status Codes (outbound):
01 à IDoc Added
30 à IDoc ready for dispatch
29 à Error in ALE service Layer
12 à Dispatch ok
03 à Data passed to port ok.
Inbound Process (Receiving System) Steps:
Do the same step as you did in sending system
ü Creating IDoc
ü Defining the Segment
ü Creating Message Type
ü Assigning the Message Type
ü Defining the Logical System
ü Assigning the Logical System
ü Creating the Distribution Model
Goto Tcode - we57:
Assign function module to IDoc type
Module: Function module
Basic type:
Message type:
Direction: 2 (inbound)
Creating Inbound process code - we42
Verifying Idoc List Tcode - we05
ALE/IDOC Status Codes (Inbound):
50 à IDoc Added
51 à Application Document not posted
64 à IDoc ready to be transferred to application
62 à IDoc passed to application
53 à Application Document posted
Useful transactions for IDocs
BD87 : Status Monitor for ALE Messages
SALE : Display ALE Customizing
WE02 : Display IDoc
WE05 : IDoc Lists
WE09 : Search for IDoc in Database
WE19 : Test tool
Check this link,
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/step%2bby%2bstep%2bprocedure%2bfor%2bcreation%2bof%2bidoc
Maybe you are looking for
-
Is raid needed for 720p DVCPro HD
Hello, my question pertains to an internal RAID 0 setup which I will use for DVDPro HD editing [720p]. Is it more likely to fail if it's internal because of the heat it causes? Would a external RAID 0 be better? I've read that hardware raid is better
-
Hi, I'm creating my first captivate 5 projects for use with a Robohelp 9 Help File using Loquendo English Speech Agent - Simon. I have experimented with pronunciation by typing text in different formats in the slide notes, this seems a lot of work
-
DSN for ODBC (RDO) connection ?
Hello ! I have an ACCESS database on a webserver and I wish to connect Crystal Report 2008 to it. Till now I have always used connection with DB on the same computer as CR so "Access/Excel (DAO)" was the way I connected to my *.mdb file. This time, w
-
I want to have a copy (jpg? psd?) of the image I see in my viewer or canvas. I can't quite figure it out, Log and Capture???? ~M
-
Hola a todos. He adquirido un nuevo MacBook Pro, y me he instalado la Suite CS4, que ya tengo en el Mac Pro de trabajo habitual. Al hacer la instalación no me pidió en ningún momento el idioma del software, si el idioma de la instalación, seleccioné