IDOC reduction for ORDERS05

Hi,
Is it possible to reduce the idoc for ORDERS05? I used BD53 and gave a new message type ZORDERS and it is asking for with reference to message type...I am not able to see orders there.
Can anyone suggest how to proceed here?Is it something that only master idoc can be reduced?Pls suggest.
Regards,
Jeyananth

If you've just tried to enter ORDERS in there, you would've seen this message:
"There is no data maintained in the reduction pool for message type ORDERS
Message no. B1121
Diagnosis
This transaction is used for maintaining and displaying reduced message types. In the standard not all message types can be reduced.
There is no data in the reduction tool for message type ORDERS.
Procedure
Use the transaction WE30 for maintaining and displaying the associated intermediate document type, or use the transaction BD60 to maintain the data for the reduction tool."
But I wouldn't recommend reducing the IDoc - it's more trouble than it's worth IMHO.

Similar Messages

IDOC reduction for MSG type MATMAS

HI all,
i have a requirement where clients need only some standard segments and some particulars staructure.We are using MATMAS as a message type and MATMAS05 as a basic type.Basically it leads us for IDOC reduction. Can someone pls help me out for getting this requirement.
Rgds,
Raghav
Edited by: raghav on Jun 9, 2009 12:28 PM

Hi,
Launch the BD53 transaction (IDoc Reduction Maintenance: Initial Screen). In the Reduced message type field, type the value ZVISTAPM_REDUCED, then press the Create button. In the popup window which appears, type in the Message type reference field the value MATMAS.
Validate.
In the next popup window, type a short description for the new reduced message type.
Validate.
In the following window, select the segments and the fields needed for the new reduced message type.
Save.
KR Jaideep,

Problem in Idoc extension for ORDERS05

HI all,
Am facing problem in inbound idoc, we have extended the Idoc ORDERS05 with one custom segment, and written the code in user exit EXIT_SAPLVEDA_001 and include ZXVEDU03 exit is triggering properly, sales orderis genarted successfull, but z-fileds are not updating in VBAK table,
so plz help....
Regards,
Suresh.D
Edited by: suresh dameruppula on Oct 20, 2009 2:39 PM

Hi Suresh,
The function exit and the include what you found is to read data from the IDOC segment into either internal table or structure.
That's the first step which you have done is part of the below set:-
EXIT_SAPLVEDA_001 & ZXVEDU03
Now you need to populate the which you have read from the idoc into the document for that you need to write the code in the below set. The below one is a function exit which will be called during the BDC. You can see this below
Aufruf Transaktion Auftragerfassung VA01                             *
call transaction Order Entry VA01                                    *
        CASE xaprau.
at line number 131 in the function module IDOC_INPUT_ORDERS.
EXIT_SAPLVEDA_002 & ZXVEDU04
Please let me know if you still have any further queries.
Thanks,
Mahesh.

IDOC format for ORDERS05

Hi all,
I have search through the web and in sap.com and I haven´t found the specification (details of fields and their meanings) for the standart idoc ORDERS05.
Does anyone on the forum knows where i can find this information?
(I have no access to a SAP system).
Thanks for all.

Structure of basic type ORDERS05
Purchasing/Sales
E1EDK01 : IDoc: Document header general data
Status: Required , min. number : 1 , max. number : 1
Structure
E1EDK14 : IDoc: Document Header Organizational Data
Status: Optional , min. number : 1 , max. number : 12
Structure
E1EDK03 : IDoc: Document header date segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK04 : IDoc: Document header taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK05 : IDoc: Document header conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDKA1 : IDoc: Document Header Partner Information
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKA3 : IDoc: Document Header Partner Information Additional Data
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDK02 : IDoc: Document header reference data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK17 : IDoc: Document Header Terms of Delivery
Status: Optional , min. number : 1 , max. number : 4
Structure
E1EDK18 : IDoc: Document Header Terms of Payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDK35 : IDoc: Document Header Additional Data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDK36 : IDOC: Doc.header payment cards
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKT1 : IDoc: Document Header Text Identification
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKT2 : IDoc: Document Header Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDP01 : IDoc: Document Item General Data
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDP02 : IDoc: Document Item Reference Data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1CUREF : CU: Reference order item / instance in configuration
Status: Optional , min. number : 1 , max. number : 1
Structure
E1ADDI1 : IDoc: Additionals
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDP03 : IDoc: Document Item Date Segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDP04 : IDoc: Document Item Taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDP05 : IDoc: Document Item Conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDPS5 : A&D: Price Scale (Quantity)
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDP20 : IDoc schedule lines
Status: Optional , min. number : 1 , max. number : 9999
Structure
E1EDPA1 : IDoc: Doc.item partner information
Status: Optional , min. number : 1 , max. number : 8
Structure
E1EDPA3 : IDoc: Document Item Partner Information Additional Data
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDP19 : IDoc: Document Item Object Identification
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDPAD : A&D: Material Exchange
Status: Optional , min. number : 1 , max. number : 1
Structure
E1TXTH1 : General Text Header
Status: Optional , min. number : 1 , max. number : 1
Structure
E1TXTP1 : General Text Segment
Status: Optional , min. number : 1 , max. number : 100
Structure
E1EDP17 : IDoc: Document item terms of delivery
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDP18 : IDoc: Document Item Terms of Payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDP35 : IDoc: Document Item Additional Data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDPT1 : IDoc: Document Item Text Identification
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDPT2 : IDoc: Document Item Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDC01 : SS: Service specifications general data
Status: Optional , min. number : 1 , max. number : 9999999
Structure
E1EDC02 : SS item: Reference data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC03 : SS item: Date segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC04 : SS item: Taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC05 : SS item: Conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDC06 : Service line formula fields
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDC07 : Service line user fields
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDCA1 : SS items: Partner information
Status: Optional , min. number : 1 , max. number : 8
Structure
E1EDC19 : SS items: Object identification
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDC17 : SS items: Terms of delivery
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDC18 : SS items: Terms of payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDCT1 : SS items: Text identification
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDCT2 : SS items: Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1CUCFG : CU: Configuration data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUINS : CU: Instance data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUPRT : CU: part-of data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUVAL : CU: Characteristic valuation
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUBLB : CU: Configuration BLOB (SCE)
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDL37 : Handling unit header
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDL39 : Control Segment for Handling Units
Status: Optional , min. number : 1 , max. number : 9
Structure
E1EDL38 : Handling Unit Header Descriptions
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDL44 : IDoc: Handling Unit Item (Delivery)
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDS01 : IDoc: Summary segment general
Status: Optional , min. number : 1 , max. number : 5

Artmas idoc reduction

Hi All,
I am trying to do idoc reduction for artmas. Did all the settings as should be done in the following order:
1)created a reduced message type (ZARTMAS) using BD53 with refernce to standard message ARTMAS.
2)Activated the changed pointers for this message type.
3)Added this message type to the distribution model
4)created partner profiles and all...
when I change an article and process it through BD21 only it says "1 master IDocs set up for message type ZARTMAS" and "0 communication IDoc(s) generated for message type ZARTMAS".
Cant think of why the idoc is not getting created.
As message type artmas belongs to BAPI RetailMaterial.Clone: even tried to create an ALE interface for the ZARTMAS message type. Still the same message.
If I do the same process for MATMAS, it works fine. Can anyone please tell whats missing or what am I doing wrong.Why is the idoc not getting created for ZARTMAS.
Thanks in advance.

Hi Fouad,
Have you looked segment E1BPE1MARARTX?
You can check this fields.
- CREATED_ON
- CREATED_BY
- LAST_CHNGE
- CHANGED_BY
- DEL_FLAG
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Idoc Reduction CREMAS

Hi,
Is there an alternative to this approach :
Problem: I create Vendor master idoc using basic type crema04 and message type cremas. Idoc reduction is present for this message type, so when the idoc is created only mandatory segment gets populated.
Solution I tried : Through BD53 , create a ZCREMAS reduction message type , select the segments to be populated , enable them and activate them . Use this message type for the generation of the idoc.
Question : Is there any alternative way to this method or this is the only way we can remove the idoc reduction for messag types?????
Thanks ,

Hi,
Perhaps you can use this custom exit '001' in include in include program LBD11F0Q to filter IDoc segment.
CALL CUSTOMER-FUNCTION '001'
 EXPORTING
 idoc_control_in = pxf_idoc_control
 target_idoc_type = target_idoctp
 target_cim_type = target_cimtyp
 IMPORTING
* idoc_control_out = pxf_idoc_control
 idoc_control_out = idoc_control_out
 TABLES
 idoc_data = pxt_idoc_data
 idoc_status = t_idoc_status.
This is being in FM MASTER_IDOC_DISTRIBUTE.
For SAP best practise, i would suggest to use reduce message type or segment filter.
Again, hope this will help.
Regards,
Ferry Lianto

Extension Idoc for ORDERS05..

Hi,
I want to add one field (VBAK-FAKSK) as an extension idoc to ORDERS05 Basic idoc type.
My problem is in this Basic type (ORDRES05) under which segment, i have to add this field (VBAK-FAKSK).
Can one help this problem would be great appreciable.
Best rgds,
srihari.V.

VBAK is the header data table for the Order.
E1EDK01 is the Main header Segment for ORDERS05 Idoc, so I think it shold go into that segment.
Refer this link for more help:
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Regards,
Ravi

Confusion on IDOC types for creation of PO

Hi,
Requirement is sending PO from sendin SAP system to receiving system.
For sending am using-
Processing code ME10
On serching forums and tutorials, i came across IDOC type- ORDERS05 but this idoc type is for both PO and SO.
PORDCR04 idoc type for creation of PO only.
Some post says PORDCR04 doesnt create PO header text.On the other hand,For inbound processing of PO idoc ( using ORDERS05 ) processing code is not available.
I will be thankful if somebody can guide me which of these idoc types is preferable.
Thanks.
Edited by: Sanjay_lnt on Jan 8, 2011 3:49 PM

Hell Sanjay
Outbound ORDERS (= Purchase Order) and inbound ORDERS (= Sales Orders) are like siblings which reflect the customer / supplier relationship.
In case of the PORDCR04 IDoc it is somewhat different because does it make sense to have the same purchase order in different system?
In our case a POS (= point of sales) system is used to create a purchase order (for replenishment) which is then converted (via SAP-PI) into an inbound PORDCR04 IDoc in the ERP system. Out of this purchase order a replenishment delivery (for the shops) is created.
Regards
Uwe

File to IDOC 4.6c (ORDERS05.ORDRSP) PI 7.11

Im reading a file through the PI file adapter and writing it to the IDOC adapter into 4.6C.
I have overwritten MESTYP in mapping in the EDIDC40 to (ORDSP) but when the IDOC is received in 4.6 the message type displays as ORDERS not ORDRSP and so the Partner Profile doesnt trigger.
<ORDERS05>
- <IDOC>
- <EDI_DC40>
<IDOCTYP>ORDERS05</IDOCTYP>
<MESTYP>ORDRSP</MESTYP>
Any help would be appreciated.

Fellas,
I am having issue with ordrsp idoc.
Currently we are receiving ack from third party for order changes. PI is configured to get idoc xml using HTTP service configured.
After PI gets the xml it calls idoc adapter to create idoc in r/3 system.
ORDRSP.ORDERS05 IDOC is already imported in PI and PI pushes it to r/3 via idoc adapter service. This interface is working in production fine. However recently sterling have started populating another control field which is <MESCOD>. R/3 is creating the idoc but not populating this particular field (MESCOD).
Their is no message mapping in PI to populate any fields. Data comes from 3rd party via HTTP and gets processed using IDOC adapter. Not sure why MESCOD is not getting populated.
Looked at message arriving in PI and can clearly see MESCOD field getting populated with right content.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <ORDERS05>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>011</MANDT>
<DIRECT>2</DIRECT>
<IDOCTYP>ORDERS05</IDOCTYP>
<MESTYP>ORDRSP</MESTYP>
<MESCOD>WEB</MESCOD> -
>>
<SNDPOR>SAPP1C</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>EDIGATEWAY</SNDPRN>
<RCVPOR>SAPR1C</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>R1CCLNT011</RCVPRN>
<CREDAT>20120213</CREDAT>
<CRETIM>000242</CRETIM>
</EDI_DC40>
Can someone please guide why would this one field not get populated when IDOC gets created in R/3 system..
Please help..
ta,
Jas

Status 51 in IDOC Basic type: ORDERS05

Hi,
When Inbound IDOCs of IDOC basic type : ORDERS05 are processed in bulk then few of the IDOCs go to status 51 with error message : "Sales organisation, Distribution channel and division cannot be determined for the customer (followed by customer number)". But when these failed IDOCs are processed again using BD87 few more IDOCs go to status 53. Similarly if the failed IDOCs are reprocessed for 4/5 times without changing any data in the IDOC then all the IDOCs go to status 53.
When I try to create a duplicate IDOC using WE19 then the IDOC goes directly to status 53. So if processed in bulk then few IDOCs go to status 51 and when processed one by one the IDOCs go to status 53 without any problem. Can someone tell me what is the reason behind it and what has to be done to avoid the continuous reprocessing of IDOC.

Hi,
When Inbound IDOCs of IDOC basic type : ORDERS05 are processed in bulk then few of the IDOCs go to status 51 with error message : "Sales organisation, Distribution channel and division cannot be determined for the customer (followed by customer number)". But when these failed IDOCs are processed again using BD87 few more IDOCs go to status 53. Similarly if the failed IDOCs are reprocessed for 4/5 times without changing any data in the IDOC then all the IDOCs go to status 53.
When I try to create a duplicate IDOC using WE19 then the IDOC goes directly to status 53. So if processed in bulk then few IDOCs go to status 51 and when processed one by one the IDOCs go to status 53 without any problem. Can someone tell me what is the reason behind it and what has to be done to avoid the continuous reprocessing of IDOC.

Processing IDOC Basic type ORDERS05 in CRM...

I'm processing (via WE19) an IDOC (Basic type ORDERS05) to create a Sales order withing CRM. I'm getting there in that a sales order is being raised, although there is no item level details so far. I know that config of the system plays a big hand in what fields within the IDOC need to be populated but has anyone actually posted/raised a Sales order in this way and can you tell me what fields within the IDOC are mandatory. Or perhaps suggest how I might derive this.
Ideally I wanted to extract a sales order and produce an outbound IDOC and then compare the contents, but I can't (don't know how) do this.
Any help would be greatly appreciated.

Hi Garry,
Here is an order from WE19, which works
        E1EDK01
     ACTION: [QUAL] - suggesting 000 - no changes
        E1EDK14
     QUALF: [QUAL] - suggesting 008 - sales org
     ORGID: [ORGANIZATION] - anything you have defined /your side/
        E1EDK03
     IDDAT: [QUAL] - suggesting 002 - delivery date
     DATUM: [DATE] - any date
        E1EDKA1
     PARVW: [QUAL] - may use AG as 'sold to' here
     PARTN: [PARTNER#] - any partner defined
        E1EDKA1      - not necessary
     PARVW: [QUAL] - may have different 'sold to' and 'ship to' or 'bill to'
     PARTN: [PARTNER#]
        E1EDP01
     POSEX [ITEM#] - for example '1'
            MENEE [Unit of measure] - PCE for peaces
                 E1EDP02
               QUALF: [QUAL] - suggesting 001 - customer order
               BELNR: [document number] - document #. any
                 E1EDP20
                WMENG: [Scheduled quantity] - any - quantity
               EDATU: [Date] - any - when to deliver
                 E1EDP19
               QUALF: [QUAL] - for example 001 - used by customer, 004 - used by manufactured
               IDTNR: [material ID] - material ID
        E1EDS01
     SUMME: [Total value of sum segment] - check for the number of lines in PO1.
Hope this helps and do not forget to allot points.
Regards,
Martin

ALE: setting up reduced IDoc type for use in 4.7 and ERP 2005 problem

I need to set up a reduced HRMD_A message type and then use it to send HR data from a 4.7 system to an ERP 2005 system.
To define the reduced type in both systems I use transaction BD53 (Idoc reduction maintenance).
The problem is that the transaction offers HRMD_A06 as the basic type on a 4.7 system and HRMD_A07 on ERP 2005. Thus i cannot set up identical definitions.
I suppose I should 'step back' to A06 at the ERP 2005 system somehow, but where to look for?..
Thank you in advance!

The table is maintained with BD69 - Assignment of message type to IDOC type.
In my case I added one line with values:
Message type: {my reduced message type}
Basic type: HRMD_A06
Extension: {my HRMD_A06 extension}
Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
SAP ERP Human Capital Management (SAP ERP HCM)

What is Ale, Edi,IDoc tech for sap

Hi all,
What is Ale, Edi,IDoc tech for sap?
Thanks.

hi deniz,
ALE
ALE
Triggering OB via Change Pointers:
 When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
Outbound Process:
When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
 To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
Asynchronous Communication:
The data that is IDocs and the function module are stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
Inbound Process:
The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
 Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
In the table TBD51 there will be entries to find which option is used.
Transactions:
SALE - IMG ALE Configuration root
 WE20 - Manually maintain partner profiles
 BD64 - Maintain customer distribution model
 BD71 - Distribute customer distribution model
 SM59 - Create RFC Destinations
 BDM5 - Consistency check (Transaction scenarios)
 BD82 Generate Partner Profiles
 BD61 Activate Change Pointers - Globally
 BD50 Activate Change Pointer for Msg Type
 BD52 Activate change pointer per change.doc object
 BD59 Allocation object type -> IDOC type
 BD56 Maintain IDOC Segment Filters
 BD53 Reduction of Message Types
 BD21 Select Change Pointer
 BD87 Status Monitor for ALE Messages
 SALE Display ALE Customizing WEDI - ALE IDoc Administration
 WE60 - IDoc documentation
 SARA - IDoc archiving (Object type IDOC)
 WE47 - IDoc status maintenance
 WE07 - IDoc statistics
BALE - ALE Distribution Administration
 WE05 - IDoc overview
 BD87 - Inbound IDoc reprocessing
 BD88 - Outbound IDoc reprocessing
 BDM2 - IDoc Trace
 BDM7 - IDoc Audit Analysis
 BD21 - Create IDocs from change pointers
 SM58 - Schedule RFC Failures
EDI
EDI(Electronic Data Interchange )
RFC DESTINATION:
 A logical name used to identify the remote system on which a function needs to be executed.
Partner Profile:
 It defines the characteristics of data being exchanged with the business partner.
Partner Function:
 Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
Partner type:
 The type of your business partner .
 EDI KU/LI
 ALE -- LS.
Archiving:
 -Need to archive the important transmitted document
-Created in SARA
 -Assigned in WE20.
PartnerProfile Tips:
 RSECHK07- Consistency check for Partner Profile.
 If you want to modify partner profile; copy it and then modify. If you cant modify it , u have to delete it.
 To move partner profile to production system choose Partner -> Transport
Port defintion:
 It defines the medium through which data is exchanged between systems.
 tRFC - Used by ALE
 FILe - Used by EDI
 R/2 system system port For R/2 system
 Internet port - to connect with internet applications
 It also depends on the receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
Startrfc - Program to execute RFC enabled Fun.mod. in SAP
EDI_DATA_INCOMING - To send data as inbound
EDI_STATUS_INCOMING - To send status to SAP
RSPARAM - To know the gateway service of the SAP system.
Message Control:
 Output controller
 A service program for determining the output type
 To generate and manage various outputs from an application and control their medium and timing of exchange.
 To retransmit the document without duplicating it
Procedure:
 A procedure defines a set of possible outputs for an application
 There may be more than one procedure but only one can be active
 Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
Output type:
Defines the characteristics and attributes of the output.
Access Sequence :
Defines a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
Sapfans Q & A
SREL_GET_NEXT_RELATIONS -
Function Module that will provide me the number of the document that was created by an IDoc
RLSUB020
Program which uses the above function module.
Upgradation problem
When the old version program is upgraded in to newer version(4.0b  4.6c) the SE38 editor wont allow u get thru the programs normally to get rid of this.
Solution:
EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
this fixes the links
ALE( Application Link Enabling )
Disk Mirroring:
Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disks contents.
Replicas:
Maintaining redundant data across multiple systems.
ALE:
It provides distributed environment to integrate non-SAP systems
Provides guaranteed delivery of data regardless of network problem to application.
Logical system :
 The systems involved in distributed environment are assigned a logical name which uniquely identifies a system in a distributed environment.
Data Mapping:
 Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
Message Types:
 Represents a business function
 Technical structure is the IDoc type
 Or can say an instance of IDoc.
IDoc :
 They are containers used to exchange data between any two process.
 It represents an IDoc type and IDoc data
 IDoc type is structure and IDoc data is an instance of it.
Pls reward if helpful.

The IDOC-SDATA for the segment E1EDP01 does not have the whole value passed

HI
I am triggring the ORDERS05 Idoc from TCode - WE19 .
In the E1EDP01 segment I have populated the quantity field , UOM field , currency field and the plant field.
I am facing the issue
1) It is not updating the plant field in R/3 orders that are created .
2) I debugged the code and found that the data for the currency field and the plant field is not being pulled in the IDOC-SDATA for the segment E1EDP01 .
Any idea why is this happening
Thanks
Nikhil

HI
I got the answer for it.
This has to be delt in the E1EDP02 segment with the qualifier value as 083 and the document value as the plant
Thanks
Nikhil

How to find the number of idocs generated for a customer on the basis of his purchase order in a day ?

How to find the number of idocs generated for a customer on the basis of his purchase order in a day ?

Dear Friends,
I am absolutely agree with your answer .
But my question is,
Lets say.....
One customer sending X number of purchase orders in a day , so how many IDocs generated on that specific day for that specific customer .
So, Question is , How can we find the no of sales orders(IDocs) generated for the customers on the specific day ?
Hope you all understood my requirement .
Thanks & Regards,
Aditya

IDOC reduction for ORDERS05

Similar Messages

Maybe you are looking for