Re: IDOC implementaion for Load Tender Notifications (EDI 204) - Outbound

Dear Members,
We started work on automating sending/receiving the Carrier Related documents from SAP at out end through EDI ( SAP 4.6C version).
Here's my requirement :
Load Tender : EDI 204 ( Development - Outbound process)
I hope that for EDI 204, we can use SAP IDOC - SHPMNT01. Could someone please guide me on whether my understanding is correct and which SAP IDOCS to use for these EDI doc?
Thanks,
Vass

Hi ,
Based on the Accredited Standards Committee (ASC) X12 format, the 204 can be used to allow shippers and other interested parties to offer (tender) a shipment to a full load (truckload) motor carrier that includes detailed scheduling, equipment requirements, commodities, and shipping instructions pertinent to a load tender. It is not to be used to provide a motor carrier with data relative to a Less-than-Truckload Bill of Lading, pick-up notification, or manifest.
Regards,
Bharani

Similar Messages

Re: IDOC implementation for Load Tender Notifications (EDI 204) - Outbound

Dear Members,
We started work on automating sending/receiving the Carrier Related documents from SAP at out end through EDI ( SAP 4.6C version).
Here's my requirement :
Load Tender : EDI 204 ( Development - Outbound process)
I hope that for EDI 204, we can use SAP IDOC - SHPMNT01. Could someone please guide me on whether my understanding is correct and which SAP IDOCS to use for these EDI doc?
Thanks,
Vass

Hi ,
Based on the Accredited Standards Committee (ASC) X12 format, the 204 can be used to allow shippers and other interested parties to offer (tender) a shipment to a full load (truckload) motor carrier that includes detailed scheduling, equipment requirements, commodities, and shipping instructions pertinent to a load tender. It is not to be used to provide a motor carrier with data relative to a Less-than-Truckload Bill of Lading, pick-up notification, or manifest.
Regards,
Bharani

Any IDoc/BAPI for Loading Material Determination Condition records - VB11??

Hi All,
I need to load the material determination condition records which can be done through the transaction VB11. I dont want to do load the records through BDC.
So, I am looking for any IDoc or BAPI which can do this job.
Any help in this regard is highly appreciated.
Points will be awarded for all useful replies.
Thanks in advance,
Surendra K

hi surendra,
i have a exact same task to load material determination to SCM
"load the material determination condition records which can be done through the transaction VB11. I dont want to do load the records through BDC, i am looking for any IDoc or BAPI which can do this job"
thank you
sridhar K

Idoc type for pm notifications

hi all,
can anyone give me names of the Idoc type for triggering pm notification.
with regards,
Syed

Ok, I found it.
FL: MDM_FUNCLOC_SAVEREPLICA
EQ: MDM_EQUIPMENT_SAVEREPLICA
Thanks!

IDOC monitor for shipping notification- EMASN

Hello experts,
Anybody know that is IDOC monitor for shipping notification-EMASN. what are the input we have to enter as defualt for this transaction.
can anybody help, very urgent.

I did not know about transaction VOFM (MAINTAIN Riquirements & Formulas), tab 'Data transfer' => 'Deliveries' .
Copy routine '301' to '931' and add thos line at the end:
likp-ntgew = xkomdlgn-ntgew_hdr.
likp-btgew = xkomdlgn-brgew_hdr.
likp-gewei = xkomdlgn-gewei_hdr.
likp-volum = xkomdlgn-volum_hdr.
likp-voleh = xkomdlgn-voleh_hdr.
Then go to VTLA ('Order to delivery copying control'), select your target (for instance 'EL' <= 'DL') and CtrlShiftF2 (Detail). Change the field Header data from '301' to our new '931'
Hope this is help someone one day,
Daniel
Edited by: Daniel Putzschler on Jan 20, 2011 2:17 PM

Idoc segment for shpmnt notification for idoc type shpmnt02

Hi gurus,
I have to find the idoc segment for shipment notification,idoc type which we are going to use is shpmnt02 or shpmnt01,Can any one of you please tell me the idoc segments for this idoc type with fields and table name?.Thanks in advance.

Hi Nagarathinam
You can use transaction WE60 for documentation on IDOCs
Best regards,
Chris

Idoc type for EDI 210

Hi ,
Is there any Basic Idoc for EDI 210 ??? Basically its an invoice . or else i have to create a custom IDoc??? Please let me know .
Thank you
Kalyan

Hi,
edi is a format of exchanging data between 2 systems.......idoc(intermediate document) is a format in which R/3 systems can communicate data with eachother....so EDI-IDOC application will be dealing with EDI format and IDOC format of R/3 data..........
Reward points
Regards

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.

IDOC error 26 for sending PO to EDI Vendor.

Hi,
I have extended ORDERS05 idoc and added 1 custom segment under parent segment E1EDKA01 for sending PO to EDI vendor.
The issue is I am not able to find a suitable EXIT to fill this segemnt. While I tried filling this segment using Enhancement Points, it gane me an error '26 - IDOC Segment could not be identified".
Please help.
Thanks,
Debi.

Hi,
Have you activated the IDoc ( extended IDoc).
Regards,
Jyothi CH.

When idoc failes for inbound sales orders then how to trigger a mail notifi

Hi All,
When idoc failes for inbound sales orders in SAP then i would like to send an email notificaiton to particular user id. Could you please let me know the settings for this requirement.
Thanks in advance..

Closing thread as there are no replies

What is iDoc Adapter for XI?

I am working on XI and came to know that I have to use iDoc Adapter for the same. I want to know
1. What is an iDoc Adapter
2. How it is used for XI
3. How to configure the same
Thanks,
Nishant

Hi Nishant,
Follow these steps................Here You can find the detailed decription...
ALE settings.
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
See the below links
Introduction to IDoc-XI-File scenario and complete walk through for starters. - IDoc to File
IDOc testing - Generate Test Case for an IDOC Scenario
Convert any flat file to any Idoc-Java Mapping - Any flat file to any Idoc
IDOCs (Multiple Types) Collection in BPM - Collection of IDoc to Single File
Introduction to IDoc-XI-File scenario and complete walk through for starters. - IDoc to File
File-XI-IDoc Scenario - File to Idoc
idoc settings Configuration steps required for posting idoc's(XI)
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - How to Support Industry Standards in XI (Part II of III) - Mapping
IDoc erros troubleshooting - Troubleshooting of ALE Process
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part III
see the below links to get more details about IDocs
ALE/ IDOC/ XML
Troubleshooting of ALE Process - Troubleshooting of ALE Process
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
Changing fields in an Idoc segment
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
serialization The specified item was not found.
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/gl_postings2.htm
http://searchsap.techtarget.com/ sDefinition/0,,sid21_gci852485,00.html - 45k - Cached - Similar pages
Process codes in IDOC
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b806743d711d1893e0000e8323c4f/frameset.htm
http://edi.stylusstudio.com/msg04418.htm
Check this link to find out the difference b/w ALE,IDOC and BAPI
http://www.sap-img.com/abap/ale-bapi.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Introduction to IDoc-XI-File scenario and complete walk through for starters.
---Split messages :
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure
Have a look at this document, which explains the settings in IDOC-File scenario,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
Regards,
Vinod.

Xslt mapping cidx message is Load Tender Motor

Hi
I am working on XSLT Mapping from the below link SAP Technical
Import corresponding XSD structure under External Definitions in IR. Here the corresponding CIDX message is Load Tender Motor.
In the above line what is CIDX, I have little bit knowledge about that, I read that in Adapters topic CIDX, PIDX this are some industry standard adapters. but how to import that Load Tender Motor in to my Scenario.
So can any body please go through that link and provide some usefull information.
Thanks
G V Anil

Hi
CIDX is adapter.use this thread for detail
About CIDX
CIDX scenario
XI CIDX

EDI Vendor outbound payment advice, idoc do not contain RE in the header

Hi,
I am facing a critical issue on EDI vendor outbound payment advice idoc. Actually the IDOCs which i created do not contain the RE in the header record. This mandatory qualifier is located just before the SAP ID. The IDOCs which i created got error out and not translate.
Example - LIRE0001000922
Can anybody tell me that how can we get this RE mentioned in the above idoc no. I want this RE to be come when the idoc is created.
Point will be awarded.

Hi Rajesh,
If everything is maintianed, i think the problem is with the file that your are uploading. Please check the file.
And also check whether the data record is maintained. For Field Name "PARTNER_Q" youa have to assign the :QualPart" RE (biil-to-party) in the data record.
Check these things and i hope it solves your problem.
And you can contact me at [email protected]
Thanks
~Rajesh

Taking much time for loading data

Dear All
While loading data in PRD system (for master data and transaction data), it's taking much time. For ex., 2LIS_05_QOITM, I am loading delta data only in PSA from R/3. Some times (yesterday) it's taking 2 mins and some times (today) it's taking 5 hrs not yet completed (it's yellow). Actually yesterday, we went to SM58 in R/3 side and executed that LUW for some other data sources. Now also we can do but we don't want to like that. Because we are expecting permanent soulution. Could u please advice me. I am getting below message in status tab
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
I am loading data through Process chain and user is BWREMOTE (authorized user).
Please help me.
Thanks a lot in advance
Raja

Dear Karthik
No I couldn't resolve till now
But Everything is fine.
Now status is yellow only (209 from 209). Now what i want to do.
Im getting below message in status tab
Missing data packages for PSA Table
Diagnosis
Data packets are missing from PSA Table . BI processing does not return any errors. The data transport from the source system to BI was probably incorrect.
Procedure
Check the tRFC overview in the source system.
You access this log using the wizard or following the menu path "Environment -> Transact. RFC -> Source System".
Error handling:
If the tRFC is incorrect, resolve the errors listed there.
Check that the source system is connected properly to BI. In particular, check the remote user authorizations in BI.
In detail tab, I am getting below message
Info IDoc 2 : sent, not arrived ; IDoc ready for dispatch (ALE service)
Thanks in advance
Raja

Take long time for loading

Hi Experts,
One of my data target (Data comming from another ODS) is taking long time for loading, basically it takes below 10 times only, but today it is running from last 40 minesu2026
In Status Tab it showing....
Job termination in source system
Diagnosis
The background job for data selection in the source system has been terminated. It is very likely that a short dump has been logged in the source system
Procedure
Read the job log in the source system. Additional information is displayed here.
To access the job log, use the monitor wizard (step-by-step analysis) or the menu path <LS>Environment -> Job Overview -> In Source System
Error correction:
Follow the instructions in the job log messages.
Can anyone please solve my problem.
Thanks in advance
David

Hi Experts,
Thanks for your answers, and my load failed when the data comes from one ODS to another ODS. find the below job log
Job started
Step 001 started (program SBIE0001, variant &0000000007169, user ID RCREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 8ZPP_OP3
 Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 20006838008 *
abap/heap_area_total.......... 20006838008 *
abap/heaplimit................ 83886080 *
zcsa/installed_languages...... ED *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 2047 *
ztta/roll_area................ 5000000 *
ztta/roll_extension........... 4294967295 *
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 1 in task 0002 (1 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:31:55, End = 06.09.2010 01:31:55
Asynchronous transmission of info IDoc 3 in task 0003 (1 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 2 in task 0004 (2 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:32:00, End = 06.09.2010 01:32:00
Asynchronous transmission of info IDoc 4 in task 0005 (2 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 3 in task 0006 (3 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:32:04, End = 06.09.2010 01:32:04
Asynchronous transmission of info IDoc 5 in task 0007 (3 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 4 in task 0008 (4 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:32:08, End = 06.09.2010 01:32:08
Asynchronous transmission of info IDoc 6 in task 0009 (4 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 5 in task 0010 (5 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:32:11, End = 06.09.2010 01:32:11
Asynchronous transmission of info IDoc 7 in task 0011 (5 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Asynchronous send of data package 13 in task 0026 (6 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:01, ARFCSTATE =
tRFC: Start = 06.09.2010 01:32:44, End = 06.09.2010 01:32:45
tRFC: Data Package = 8, TID = 0AEB465C00AE4C847CEA0070, Duration = 00:00:17,
tRFC: Start = 06.09.2010 01:32:29, End = 06.09.2010 01:32:46
Asynchronous transmission of info IDoc 15 in task 0027 (5 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 14 in task 0028 (6 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:32:48, End = 06.09.2010 01:32:48
tRFC: Data Package = 9, TID = 0AEB465C00AE4C847CEF0071, Duration = 00:00:18,
tRFC: Start = 06.09.2010 01:32:33, End = 06.09.2010 01:32:51
Asynchronous transmission of info IDoc 16 in task 0029 (5 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 15 in task 0030 (6 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:32:52, End = 06.09.2010 01:32:52
Asynchronous transmission of info IDoc 17 in task 0031 (6 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 16 in task 0032 (7 parallel tasks)
tRFC: Data Package = 10, TID = 0AEB465C00684C847CF30070, Duration = 00:00:18,
tRFC: Start = 06.09.2010 01:32:37, End = 06.09.2010 01:32:55
tRFC: Data Package = 11, TID = 0AEB465C02E14C847CF70083, Duration = 00:00:17,
tRFC: Start = 06.09.2010 01:32:42, End = 06.09.2010 01:32:59
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:32:56, End = 06.09.2010 01:32:56
Asynchronous transmission of info IDoc 18 in task 0033 (5 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 17 in task 0034 (6 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:33:00, End = 06.09.2010 01:33:00
tRFC: Data Package = 12, TID = 0AEB465C00AE4C847CFB0072, Duration = 00:00:16,
tRFC: Start = 06.09.2010 01:32:46, End = 06.09.2010 01:33:02
Asynchronous transmission of info IDoc 19 in task 0035 (5 parallel tasks)
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 100,000 records
Result of customer enhancement: 100,000 records
Asynchronous send of data package 18 in task 0036 (6 parallel tasks)
tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =
tRFC: Start = 06.09.2010 01:33:04, End = 06.09.2010 01:33:04
Asynchronous transmission of info IDoc 20 in task 0037 (6 parallel tasks)
ABAP/4 processor: DBIF_RSQL_SQL_ERROR
Job cancelled
Thanks
Daivd
Edited by: david Rathod on Sep 6, 2010 12:04 PM

Re: IDOC implementaion for Load Tender Notifications (EDI 204) - Outbound

Similar Messages

Maybe you are looking for