Improve Triggering Time for outbound IDOCs

Hi,
We have a requirement where in we have to transfer some material master data from Production system to a Testing system.
We schedule a background job for BD10 in the Production system which generates IDOCs for the material data.
Similarly, after we get this IDOC in the Testing system, we run RBDAPP01 to process the IDOCs.
Now the problem is, the IDOCs are getting generated in the Production system quickly and we can see the status of the IDOCs as 03 which means IDOCs
are sent from the production system. But it takes too long for us to see the IDOC in the testing system.
( We sent some 50000 IDOCs from Production System and after 6 hours, we can see only 20,000 IDOCs in the Testing system. )
Any idea how we can reduce this time? Is there any background program scheduled for the IDOCs to be sent from one system to another, where in we can change the frequency ?
After changing the output mode in the partner profile from TRANSFER IDOC IMME to COLLECT IDOCS , and increasing the packet size, we see some improvement.
But can it be improved further?
Any pointers to this is highly appreciated.
Regards,
Suganya

Hi,
One thing you cand do is use the Parallem Proc option of the program RBDAPP01 This way the IDocs will be processsed parallelly instead of sequentially. Take a look at the documentation of the program for parallel proc. And remember with parallel processing, large packet sizes lowers the level of parallel processing.
I hope you are specifying the the message type in the selection screen on the program RBDAPP01so that it processes only MATMAS messages.
Hope this helps
regards,
Advait

Similar Messages

Issue in Partner Profile config for Outbound IDOC

Hi Experts,
I have requirement like, When ever there will be any change in a Sales Order an Outbound IDOC will get triggered though a output type. This IDOC will save a file in the Application Server.
The Message Type i am using is ORDERS and the Basic Type is ORDERS05.
I have created a Partner Profile also a Receiver Port of type FILE.
I have Assigned Message type in Outbound Parameters.
I have assigned Receiver Port and Basic type under "Outbound Option".
I have Assigned Applications as 'V', Message type as 'Output Type' and Process Code under "Message Control".
When i am changing any Sales Order no IDOC is getting Triggered. I checked the Sales Order>Extras> Output> Header> Edit, the Output type is in Status RED with Message " No Partner Profiles (Message Control) Maintained".
Please guide me if i have missed any configs.
Help me solving this issue.
Thanks in Advance!
Priyabrata

Hi Priyabrata,
please try changing in your partner profile the application from V to V1. Another problem that's often causing the partner profile not to be found are the partner functions that are added automatically by SAP, but sometimes forgotten in the partner profile.
I don't have a SAP system at the moment, but as far as I remember the long text of the message indicates the partner profile parameters that SAP uses for the lookup.
If all of this doesn't help, I'd quickly debug this and see why SAP's not picking up the correct partner profile.
Cheers, harald

Triggering of DESADV Outbound IDOC

Hi Gurus,
can anyone assist me in telling the process involved and steps to trigger DESADV type Outbound IDOC of type 856
thanks in advance;
Sunil

Go to NACE and select V2 and click output type from menu.
Give following value.
Condition component Value
Access sequence 0005 (sales organization/customer)
Condition 0 (no condition)
"Exclusive" select
Output type LAVA (shipping notification outbound)
Procedure V10000 (shipping output)
Application V2 (shipping)
Processing subroutine Program RSNASTED,
form routine EDI-PROCESSING
General data Select Condition access and Multiple sending of output, otherwise
leave the fields blank
Time e.g . 4 (immediately, IDocs are generated immediately after
posting)
Transmission medium 6
Partner function WE
Language DE (German)
You must maintain following values for outbound partner profile.
Message type : Desadv
Partner type : Ku
Partner function : WE
Port : Subsystem
Outbput mode: Collect idoc
Basic type : Delvry01
Packet size: 1
Application: V2
Output type : LAVA
Process code: DELV.
You can post the delivery by selecting Logistics ??Sales and Distribution ??Shipping, Delivery
-->Create (transaction VL01). Output control is used to find the condition record and the shipping
notification is sent to the customer via EDI (IDoc Interface). The shipping time in the condition
record determines when the corresponding outbound IDoc is generated
On the Create Condition Records (Outg. ship notifica.): Fast Entry screen:
-->Enter customer number in Customer, SAP Ship-to # .
-->Enter WE in PartF.
-->Enter 6 in Medium.
-->Enter 4 in Time.
-->Enter EN in Language.
-->Choose Save.
Thanks,
Narayanan

FM for Outbound Idoc

Hi ..
Actually we are looking for the function module for the Outbound Idoc segment - BOMMAT in Bill of material . we need to know which is the correct FM to be used.Please help me with this.

Hi,
Check if you can use FM- MASTER_IDOC_CREATE_BOMMAT.
Regards,
Anup

Query on User exit for outbound idoc

Hi ,
Can u all pls help me out to solve these queries
1. when we extend a new segment (at we31) and create a new idoc type(at we30), say,for DELVRY05 idoc type-what is the logic to be written inside the Exit(at Transaction code - CMOD -where a project is created and the exit is found for the enhancement) ,to view our extended segment -that needs to be appended (viewed below the existing segment)at we02?
2.Can we delete the outbound idoc generated with errors from development server?
3.How to recify the outbound idoc errors-like runtime,syntax,port unreachable errors(at the status record and data records listed inside we02 transaction code)?
4.How to check values populated at our extended segment inside we02-Transaction code.
say,the logic required inside the exit may be,
Select single ladel from eikp into wa_ladel where refnr = (inbound delivery)
In this,the ladel exists in eikp table as EIKP-LADEL field.
The main thing is- an inbound delivery is created at transaction code VL31N for which an outbound idoc(using an Exit )should be generated with few more validations for the fields like
i) ekpo-pstyp(corresponding IDOC segments are E1EDL26-PSTYV )
ii)ekko-lifnr and ekko-lichn(E1EDL24-LICHN )
Segment name-item(at transaction we63) Segment no.
iii) E1TXTP8-TDLINE => SCAC Code. 11
 E1TXTH8-TDID => Z001. 10
iv) E1TXTP8- TDLINE => Primary seal number. 13
 E1TXTH8-TDID => Z002. 12
v) E1TXTP8- TDLINE => Secondary seal number. 15
 E1TXTH8-TDID => Z003. 14
5.Can you help me out to know the logic by which we can validate few fields from different tables like eikp,ekpo and ekko inside our Exit (in the project created at CMOD transaction?
With Regards,
Srividya

Hi Swati Choudhary,
please ask your question in devlopment forum, please see its 2 yr old thread, and i don;t think Phileas Fogg still remember his stuffs.

Segment creation for outbound Idocs to non-SAP system

Hi,
I need to create a custom idoc for outbound interface to a non-SAP system. Here I need to create segments. So, should I create the fields in the segment with the attributes of fields in non-SAP system or fields attributes should be of SAP system.
For example:
There is a field invoice number which is of 10 Chars in SAP but in legacy it is divided into 2 fields: invoice prefix of 2 chars and invoice no. of 8 chars. Should my segment contain one invoice field of 10 chars or should it be two fields with 2 and 8 chars?
In general, always should the segment fields contain field attributes based on receiving system?
Thanks in advance.
Sriram.

Hi
Should my segment contain one invoice field of 10 chars or should it be two fields with 2 and 8 chars?
I think it shoild be better to have 2 fields, but probably the result will be the same if you send the idoc by a text file, because both informations should be contiguos, I mean if you have file with a record like this:
1234567890
This record can be obtained downloading a segment with 2 fields:
FIELD1 = '12'
FIELD2 = '34567890'.
or single field:
FIELD = '1234567890'.
So it'll be the same for tje target system
In general, always should the segment fields contain field attributes based on receiving system?
It depends on who has to convert the idoc to the right format for the target system
I mean you can create a "SAP" Idoc, so the receiving system will have to convert it to the right format
or
you can send the idoc in the right format, so the receiving system doesn't need to convert it
Max

Error Handling for Outbound IDOC - COSMAS (Cost Center Master)

Hi,
I need to trigger a mail to SAP inbox whenever a outbound idoc fails for any reason.
I know how to do it for inbound or outbound transaction data, but not sure how to do error handling for outbound master data.
Could one of you help me understand the same.
Thanks in Advance,
Vinoth

Hey Vinoth,
Do you want decide the recipient of the mail dynamically? am asking because if you give the USER NAME in the partner profile and when ever a IDOC fails a mail will automatically reach the user inbox automatically
let me know if i answered ur question.
Thanks,
Santhosh

Process code for Outbound IDOC type MBGMCR03

Hi Friends,
I have a requirement, where in Goods receipt IDOC data from ECC 6.0 needs to be sent to the external system through XI, for that require a process code. Can you all suggest the process code for the outbound IDOC for Goods Receipt.
Thanks in Advance,
Meghna.

Hi,
Goods Movement is genarally inbound.
You may have to write your own process code for MBGMCR03.
Regards,
Shakthi.

ALE configuration for Outbound Idoc - Help me

Hi Experts,
I am newbee in SAP and XI. I was trying to send MATMAS Idoc from R3 and i was running into some issues. So i would appreciate if someone can help me.
I am using following link as reference. /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I did all the steps mentioned in the above link ( Creating Logical Systems, Assigning Client and RFC destnations, Creating distribution models ..... etc)
and then everything went well and i saw success messags in all the steps.
I used BD10 to send material and it went well. But when i check TRFC queue, i see some error messages; "No service for system SAPRDI, client 800 in Integrion Directory"
And all the messages are hanging in the TRFC queue.
Note: I havent configured anything in XI yet. I wanted to make sure IDoc gets to XI client first.
Thank you in advance. Pls help me its very urgent.
Thanks,
Surya

I created RFC destination (SM59) and Port (IDX1)
Then i sent another material (BD10) and checked tRFC queue. i found bunch of error in the Queue.
1.connection to host 10.4.23.120, service sapgw00 timed out / CPI-C error C
No service for system SAPRDI, client 800 in Integration Directory
partner not reached (host 10.16.176.29, service sapgw00) / CPI-C error CM
connection to host 10.16.136.127, service sapgw58 timed out / CPI-C error
Note: i have noticed entries for R3 in SLD as below
System Name: RDI ( not SAPRDI as mentioned in the error message)
System Home: r3ides
That might be reason. If so, how to change it in R3 box? Any suggestions?
Please send me if you guys have any links or docs to address this issue.
Thanks,
Surya

Process Code for Outbound Idoc

Hi All,
We need to find out the Process Code for an Idoc.
Note : We dont have access to WE41, WE20 ,BD51.
Could you please suggest any alternatives.
Thanks,
Sanjeet

Hi Gautham,
Thanks for ur reply.
But still we hv not *** to the solution.
We have available information as following:
Basic Type : DESADV01
Extension Type : EXTDES03
Message type : DESADV
Partner NUmber : XXXXXX
Partner Type : KU
I checked in Table TMSG1 and i got more than one similar process codes for the same message type.
Actually I have the generated Idoc number and we are trying to reach to the FM which populates the Idoc segments.
So if we get the process code, we can reach to FM.
Thanks,
Sanjeet

Steps to configure p.o for outbound IDOC

gurus
donno much about idocs i want to configure my p,o to be sent to vendor through edi using idoc.
can some one help me to update the relevent data,
what step one have to take very first time going to use idoc for p,o
thanks

Hi,
Go to SPRO > MM > Purchasing > Messages > EDI > Set Up Partner Profile (WE20) - here create partner profile with following details;
Partner Type - "LI"
Under Outbound parmtrs.: -
Partner Role EI + Message Type ORDERS and double click on this and maintain following;
Output options: -
Receiver port        SAPGED
Basic type           ORDERS05
View                 ORDERSWOCON1
Activate "Cancel process after syntax error"
Message Control: -
    Application        EF : Purchase Order
    Message Type:      ZEDI : EDI PO Output
    Process Code       ME10 : ORDERS: Purchase order
Go to SPRO > MM > Purchasing > Messages > Output Control > Message Types > Define Message Types for Purchase Order
> Maintain Message Types for PO - Here Take copy of NEU and create your own Output Type as "ZEDI" for EDI Processing and maintain following parameters;
Dialog Structure - Under "Processing Routines", maintain Program - "RSNASTED" and Form Routine - "EDI_PROCESSING"
Dialog Structure - Under "Partner Roles", maintain Medium as "6" and Function as "EI"
Under Default Values Tab;
Dispatch time - 4
Transmission Medium - 6
Partner Function - EI
> Fine-Tuned Control: Purchase Order - Here add o/p type "ZEDI" with operation "1" and save.
Go to SPRO > MM > Purchasing > Messages > Output Control > Message Determination Schemas > Define Message Schema for Purchase Order - Maintain Message Determination Schema: Purchase Order - here add o/p type "ZEDI' in schema grp "RMBEF1"
Now maintain Po o/p condition record for ZEDI in MN04.
Create PO and check the output.

Error handling for outbound idoc

could you tell how to handle an outboun idoc error

Hi Jaya Krishna,
The Outbound erroe occurs because of so many reasons.It may be due to less repetations of data in segment , or if reciever is not available . U can process the IDOC-Outboubnd with help of following TCODES
1. TO check status - we02
2. To get list of process codes for Inbnd and Outbnd IDOCs - we64
3. TO check IDOC is sent to receiver or not- sm58
4. To trace IDOC - bdm2
5.To check status of tRFC executiojn- bd75
Followins is the very useful blog to solve your all problems , refer to that
1. /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
2. /people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
Regards.
Note: Reward if useful

Transactional RFC fails for Outbound IDoc

Hi,
I am trying to send out an IDoc to XI 3.0 system from an R/3 4.6 C system and I get the following error :
"No service for system SAP<SYSID>, client nnn in Integration directory, when the system tries to send the out the IDoc." Any idea what that means ? The Business sytem for the client is defined in the SLD and imported into the ID.
I am able to run a similar scenario (same IDOC type) from a different system. So I know the steps I am following are right.
Thanks for help,
Regards

I have already defined the technical system and business system for the sender R/3 system. And I have also created the service by assigning the business system for the specific client of sender business system in the ID (Configuration).
The receiver port in the Integration server (SAP<SID>_NNN> is also defined and the IDOC type already imported.
Do I need to do more ? BTW , we did not run RZ70 on the sender system as the t-code is not available. Does it come with some patch/Addon. We defined the system on SLD manually.
Thanks for your response.
Regards,
Durga

Output determination for outbound Idoc WMMBXY

Hi,
I need to send Idoc only when material movements with certain types are posted. The problem is that standard condition record for application ME does not contain field BWART. Did you manage to extend it?
Kind regards,
Radek

Hi Ganesh Ram
Use Out type SHOR with Access sequence--- DlvType/Shipping Point
Thanks
Ramesh

How to improve lag time for WVC-210 for remote viewing

Hi,
My 2 camera WVC-210 is all setup. When I operate the camera remotely, I instanly hear the lens motor operate but there is aproximately 30 to 60 seconds lag time before the video is refreshed. This can be very frustrating at time. I have both cameras set up wireless.
Can somebody first explain to me why this happens and what I can do to improve the lag time. Perhaps I should tweak some settings. I would also consider buying what ever gadget is needed to make it work better.
Just to review my problem. Sound is instant but video lags.
Thank you all in advance,
Rod

May I ask if this is also happening if you’re not viewing the camera remotely? Have yoy tried adjusting the sensitivity of the WVC210?

Improve Triggering Time for outbound IDOCs

Similar Messages

Maybe you are looking for