Help out for Inbound & Outbound queue

BW Gurus
pl. help me on Inbound & Outbound queue, give details as step by step or any document pl. send it on [email protected]
but i want to understand the through process of it.
assign points if helpful
thanks in advance
charu

http://help.sap.com/saphelp_nw04/helpdata/en/e7/555e3c0f51a830e10000000a114084/content.htm
You can check the tRFCs using tcode SM58 ,and analyze it.
Outbound queue is something which maintains data when it gets posted to R/3. You can check Outbound queue using tcode LBWQ. We generally load the LBWQ data to Delta Queue using JoB Controller.
WE20 is tocode where you maintain Inbound n Outbound parameters. Like which messages to communicate in between Bw & R/3 system.

Similar Messages

AS2(SOA-B2B) Channel Setup for Inbound/Outbound

Hi
Can anyone share a document on how to setup AS2(SOA-B2B) Channel Setup for Inbound/Outbound? We are trying to configure AS2 (SSL), but test with partner is failing.. any document would help...
Appreciate your help
--Sri

One options is to use a java callout in the inbound agreement.
Ismail M.

Need sample programs for inbound & outbound interfaces in abap hr?

hi friends
i need sample programs for inbound & outbound interface programs in hr abap . any one send me pls
thanks & regards
deepurd

&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Report ZPROG65_11 *
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
REPORT zprog65_11 .
TABLES : lfa1.
TYPES : BEGIN OF ven ,
lifnr LIKE rf02k-lifnr,
bukrs LIKE rf02k-bukrs ,
ekorg LIKE rf02k-ekorg,
ktokk LIKE rf02k-ktokk,
name1 LIKE lfa1-name1,
sortl LIKE lfa1-sortl,
land1 LIKE lfa1-land1,
spars LIKE lfa1-spras,
akont LIKE lfb1-akont,
fdgrv LIKE lfb1-fdgrv,
waers LIKE lfm1-waers,
anred LIKE lfa1-anred ,
END OF ven .
DATA : t_ven TYPE TABLE OF ven WITH HEADER LINE ,
t_bdc LIKE TABLE OF bdcdata WITH HEADER LINE .
DATA : v_file TYPE string ,
v_temp TYPE i ,
v_lifnr(10) TYPE n,
v_hdate LIKE sy-datum.
DATA : c_tcode LIKE sy-tcode .u201Dvalue u2018XK01u2032.
PARAMETERS : p_file(30) DEFAULT u2018c:\vendor1_11.txtu2019,
p_group LIKE apqi-groupid.
START-OF-SELECTION .
MOVE p_file TO v_file .
PERFORM file_upload TABLES t_ven USING v_file .
v_hdate = sy-datum - 1.
CALL FUNCTION u2018BDC_OPEN_GROUPu2019
EXPORTING
client = sy-mandt
DEST = FILLER8
group = p_group
holddate = v_hdate
keep = u2018Xu2019
user = sy-uname
IMPORTING
QID =
EXCEPTIONS
client_invalid = 1
destination_invalid = 2
group_invalid = 3
OTHERS = 11
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT t_ven .
clear lfa1.
v_temp = 0.
MOVE t_ven-lifnr TO v_lifnr.
SELECT SINGLE * FROM lfa1 INTO lfa1 WHERE lifnr =
v_lifnr.
IF sy-subrc = 0.
WRITE :/ u2018foundu2019.
v_temp = 1.
else.
write: / u2018not foundu2019.
ENDIF.
IF v_temp = 0.
c_tcode = u2018xk01u2032.
PERFORM fill_ddc_table .
ELSEIF v_temp = 1.
c_tcode = u2018xk02u2032.
PERFORM fill_bdc_table .
ENDIF.
CALL FUNCTION u2018BDC_INSERTu2019
EXPORTING
tcode = c_tcode
TABLES
dynprotab = t_bdc
EXCEPTIONS
internal_error = 1
OTHERS = 7.
REFRESH t_bdc .
ENDLOOP .
CALL FUNCTION u2018BDC_CLOSE_GROUPu2019
EXCEPTIONS
not_open = 1
queue_error = 2
OTHERS = 3.
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form file_upload
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013>P_T_VEN text
u2013>P_V_FILE text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM file_upload TABLES p_tven STRUCTURE t_ven
USING p_vfile.
CALL FUNCTION u2018GUI_UPLOADu2019
EXPORTING
filename = p_vfile
filetype = u2018ASCu2019
has_field_separator = u2018Xu2019
IMPORTING
FILELENGTH =
HEADER =
TABLES
data_tab = p_tven
EXCEPTIONS
file_open_error = 1
file_read_error = 2
OTHERS = 17
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. u201D file_upload
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form FILL_DDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013> p1 text
<u2013 p2 text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM fill_ddc_table .
SCREN 100
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180100u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-LIFNRu2019.
t_bdc-fval = t_ven-lifnr .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-BUKRSu2019.
t_bdc-fval = t_ven-bukrs.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-EKORGu2019.
t_bdc-fval = t_ven-ekorg.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-KTOKKu2019.
t_bdc-fval = t_ven-ktokk.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
110
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180110u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-NAME1u2032.
t_bdc-fval = t_ven-name1 .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SORTLu2019.
t_bdc-fval = t_ven-sortl.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-LAND1u2032.
t_bdc-fval = t_ven-land1.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SPRASu2019.
t_bdc-fval = t_ven-spars.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
120
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180120u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
130
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180130u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=ENTRu2019.
APPEND t_bdc. CLEAR t_bdc.
210
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180210u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFB1-AKONTu2019.
t_bdc-fval = t_ven-akont .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFB1-FDGRVu2019.
t_bdc-fval = t_ven-fdgrv.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
215
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180215u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
220
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180220u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
310
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180310u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFM1-WAERSu2019.
t_bdc-fval = t_ven-waers .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
320
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180320u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=UPDAu2019.
APPEND t_bdc. CLEAR t_bdc.
ENDFORM. u201CFILL_DDC_TABLE
u201D FILL_DDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form FILL_BDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013> p1 text
<u2013 p2 text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM fill_bdc_table .
SCREN 101
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180101u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-LIFNRu2019.
t_bdc-fval = t_ven-lifnr .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-BUKRSu2019.
t_bdc-fval = t_ven-bukrs.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-EKORGu2019.
t_bdc-fval = t_ven-ekorg.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
110
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180110u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018lfa1-anredu2019.
t_bdc-fval = t_ven-anred .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-NAME1u2032.
t_bdc-fval = t_ven-name1 .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SORTLu2019.
t_bdc-fval = t_ven-sortl.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-LAND1u2032.
t_bdc-fval = t_ven-land1.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SPRASu2019.
t_bdc-fval = t_ven-spars.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
300
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180300u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=YESu2019.
APPEND t_bdc. CLEAR t_bdc.
ENDFORM. u201D FILL_BDC_TABLE
Best Regards

Help with status of inbound/outbound queues

Hello SDN XI experts!
I hope one of you can offer some assistance with an XI issue we have, as we currently have no XI resource on site and we're stuck in dire straits!
We have had some problems with our inbound and outbound queues in XI, and a search of the net and SDN hasn't helped yet. Basically, if I go in to transaction SMQ1 or SMQ2, I can see that there are files (or do you call them messages?) are building up in our queues with the status READY. To process these files through XI, I am going in to transaction SMQ1 and SMQ2 periodically, and activating the queue. This sets the status to RUNNING, and the files/messages are processed successfully.
What I'm after is how do I either:
a) set the queues so that they are always in status RUNNING;
b) schedule a job to activate the queues periodically; or
c) is there some other thing I am missing?
Sorry if this is a bit vague, but I have no experience of XI at all. If I haven't provided enough info, please ask some questions. Anything you can do to help would be great as I'm manually doing this ten times a day and it's getting tiresome!

Thanks for all your help guys, it's much appreciated as I have ZERO experience with XI...
I have uploaded a screenshot of SMQR to the web, apologies for the quality, but I only have MS Paint on this desktop:
http://img405.imageshack.us/img405/7202/smqrws8.jpg
Luckily, some files have started to queue up again, so I could take some more screen shots! Here is the view of SMQ2:
http://img166.imageshack.us/img166/7086/smq2mv6.jpg
And then when I double click a queue, you see this screen with the queue in the status READY:
http://img248.imageshack.us/img248/3935/smq22ed6.jpg
Until I go in to SMQ2, double click the queue, highlight it and press activate, the files/messages will just stay in XI. After I press the Activate button on the application toolbar in the third image, the files are processed successfully. i.e. If you go in to SXMB_MONI they have a little chequered flag next to them.
Thanks for all your time guys, points will be awarded if you can help me out!

Transaction codes for inbound/outbound of ALE-ITS URGENT

Hi All,
antbody can plz tell me the transaction codes for inbound and outbound process and also plz tell me ALE Message T-Codes.
Thanks,
Maheedhar.T

Under the WEDI and BALE, area menus you will be able to find all the transaction codes pertaining to the ALE.
SALE, WE30, WE31, WE20, WE02, WE21, WE81, WE82, WE41, WE42 etc are the transactins that will help you in configuring ALE.
Regards,
Ravi
Note- Please mark all the helpful answers

Urgent help- How to open Outbound queues

Hi,
I am new to SCM-APO, we have SCM 5.0 having CIF to R/3 4.7 Enterprise.
In SMQ1 i can see lot of outbound queues present with status NOSEND in R/3.
I want to push these queue manually how shoild i do it
Please guide me as i m new to this area.
Thanks
Amit

Hi Amit,
Go to Transaction /n/sapapo/ccr i.e.CIF Comparision/Reconcillation of Transaction Data. then Click on
Execute Comparision/Reconcillation Tab. Then Enter Parter System i.e ECC,then Proudct & Location.then Select Document to be checked like Production Order i.e Mfg Ordrs(with Reqs/Receipt , with Opernations),Planned Order,Purchase order etc. which you want to Transfer in ECC concern to the Product.Then Execute the Transaction.
You will find Transaction data & result Documnet.Open the Transaction Data i.e Mfg Orders or Planned Orders.Then double click on Requirements/Receipts or Operations.You will find the objects in right hand side.Select all the objects & push in to R/3 with Push button R/3.
Hope so it will help you to solve your problem.
Regards
Sujay

Recommended Status Codes usage for Inbound & Outbound IDocs

Hi,
Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
I assume we use 51 for Posting Program (not 56) and
26 for a Z-Selection Program (Not 37 or any other Code).
Please let me know what is recommended and which status codes most of the people use while Custom Development.
Thanks and Regards,
Venkat.

Hi,
Outbound IDOC Status Codes
The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
Outbound IDOCs
Code Error Event Severity SAP Meaning
02 Yes Error Error passing data to port
03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
04 Yes Error Control information of EDI subsystem
05 Yes Error Translation
06 No Harmless Translation
07 Yes Error Syntax check
08 No Harmless Syntax check
09 Yes Error Interchange handling
10 No Harmless Interchange handling
11 Yes Error Dispatch
12, 13, 14 No Harmless OK
15 Yes Warning Interchange acknowledgement negative
16 No Harmless Functional acknowledgement
17 Yes Warning Functional acknowledgement negative
18 No Harmless Triggering EDI subsystem
20 Yes Error Triggering EDI subsystem
22 No Harmless Dispatch OK, acknowledgement still due
23 Yes Error Retransmission
24 No Harmless Control information of EDI subsystem
25 Yes Warning Processing despite syntax error
26 Yes Error Syntax check
27 Yes Error ALE error
29 Yes Error Error in ALE services
30 No Harmless Ready for dispatch (ALE)
31 No Harmless IDOC is marked for deletion
33 No Harmless Original of an IDOC which was edited
34 Yes Error Error in control record of IDOC
36 Yes Error Timeout error; electronic signature not performed
37 Yes Error IDOC added incorrectly
38 No Harmless IDOC archived
39 No Harmless Receive confirmed
40 Yes Error Application document not created in target system
41 No Harmless Application document created in target document
Inbound IDOC Status Codes
The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
Inbound IDOCs
Code Error Event Severity SAP Meaning
51, 52 Yes Error Posting error
53 No Harmless Posting successful
54 Yes Error Error during formal application check
55 No Harmless Formal application check
56 Yes Error IDOC with error added
60 Yes Error Syntax error
61 Yes Warning Processing despite syntax error
62 No Harmless IDOC passed to application
63 Yes Error Error passing IDOC to application
64 No Harmless IDOC ready to be passed to application
65 Yes Error ALE error
68 No Harmless IDOC is marked for deletion
70 No Harmless Original of an IDOC which was edited
73 No Harmless IDOC archived
Regards,
Raj.

Outbound Queue help

Hello Experts,
We use XI for data replication from CRM to R/3. Now because of error in one outbound queue all the remaining queues are getting stuck. We want to do this, even if there is an error in one queue we should be able to process the remaining queues. for example, Queue 1 has some error and we have 100 queues, so other we should be able to process other 99 queues without any problem. Its consuming so much time.
Please reply.
Points will be rewarded generousely.
Sajjan

help out for Inbound & Outbound queue

SMQ1 outbound queue

Hi Experts,
Could you please let me know the purpose of SMQ1 and SMQ2.
Because when i saw the transaction SMQ1 i am able to see even the queues for
0FI_GL_6
0FI_GL_7
1_CO_PA333ZPAC4.
But when i saw the transaction LBWQ it only contains the Logistics related extract structures.i am aware of LBWQ where the user postings will be saved here with the help of VI Update.
Regards,
Sunil Kumar.B

Hi,
SMQ1 and SMQ2 is used to view the Outbound and Inbound Queue :-
SMQ1 u2013 qRFC Monitor for the outbound queue You use this transaction to monitor the status of the LUWs in the outbound queue and restart any hanging queues manually.
SMQ2 u2013 qRFC Monitor for the inbound queue. You use this transaction to monitor the status of the LUWs in the outbound queue.
You can get more help from following link :-
http://help.sap.com/saphelp_nw04/helpdata/en/76/e12041c877f623e10000000a155106/content.htm
Navesh

Help needed for OSM - EBS Projects Integaration

Hi All,
Can anyone help me with where to start from and how to proceed regarding the integration of OSM and EBS Projects??
We have a requirement of Creating Projects in EBS through an Order created in Siebel and passed on to OSM.. Can anyone guide me how to proceed in this regard?
We are planning to create a process with an Automation Task and an Automation Plugin (Query Sender) that will trigger the EBS Projects. Is that right?
Any help in this regard will be valued. Thanks in advance.
Regards,
Hariharan

Hi Hariharan:
The proper wayt to extend O2A at COM level falls into the "Add a New Fulfillment Function" extensibility use case.
This is if you want to levarge COM Order Management including orchestration, lifecycle management and fallout management.
-Do you need to interact with EBS for various order types? new / revision, cancelation? (add, update, delete )?
-Do you need to centrally manage EBS order fallouts?
-Do you need to include EBS order items status in the overall SalesOrder status update to CRM?
Adding a New COM Fulfillment Function to the O2A Solution will translate into these high level steps:
-Determine integration approach (AIA vrs Custom System Integration ) // Assuming AIA based integration
-Define/create inbound/outbound queues (local OSM ) and AIA integration (SAF or Bridges)
-Configure new order components specifications
-new system component //EBS System
-new function component //EBSOrderFunction
- Define the new process flow to execute new function
     automation plug-in to createEBM, and receive ResponseEBM (correlate by JMSCorrelationID/XML Body)
     Here is where Brian's comment applies. As long as the automate task sets the proper correlationID in the sender plug-in
          the correspondng external receiver plg-in will process the response from EBS
- Update ProductSpecifications (to include new fulfillment funtion in orchestration plans)
- Update Decomposition Rules to decompose relevant items for new EBM system
- Small XML and XQuery Configuration updates.
Again, this is just a high level list of steps.
Offcourse this list will grow into a more detailed design specification when these requirements are fully analyzed.
If you are interested you could check getting in touch with Oracle Univeristy regarding a 5-day OSM Foundation III Course, to learn about O2A and extensiblity use cases.
Course: OSM Foundations III: AIA Order to Activate Solution
http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getCourseDesc?dc=D73768GC10
[This topic is covered in "Add New Fulfillment System/Function" lesson ]
In the mean time, check this similar discussion:
Re: OSM: Modify Order To Activate Cartridge: Manage product specifications
Carlos

UTP - Test Plans IDOCs - Inbound -Outbound

Hi All,
can some one please provide the samples of standard UTP - Test plans for INBOUND & OUTBOUND IDOC interfaces, if you have such.
Regards,
Sridhar

Hi,
I am also in need of UTP for outbound IDoc.
Please forward me to my id : [email protected]
Your help would be appreciated.
Thanks,
Sangeetha

Cannot debug outbound queue

Recreate the BDOC for the BP, by running the transaction CRMM_BUPA_SEND
1. Display the BDOC in SMW01
2. Enter /h in the transaction code field
3. Press the 'retry to process message' button.
4. In the debugger - select the Settings button and 'In background task
do not process'
5. Enter F8
6. Create a new session for the outbound queue (/osmq1) there will be
an entry R3AUBUPA*** or CSA_BUPA**
7. Double-Click on this queue entry twice and choose Debug for the
CRM_UPLOAD_TRIGGER
8. In the debugger, set a breakpoint at statement 'CALL TRANSACTION' and then press F8.
9. At this statement double-click on the statement CALL_TRANSACTION and
change the variable CALL_TRANSACTION_MODE from N to A, press the
'change field content' button and then press F8
10. Now you will be in the R/3 System and you can see the batch input
screen for this customer and you will then be prompted for the
missing field in the BDOC.
When the field has been identified, please maintain this field in CRM
and then reprocess the error BDOC.

Hi Stephen,
The user is a dialog user. Moreover, I have manually put an external breakpoint where it calls the function module CRM_UPLOAD_TRIGGER and debug the application when I go click on save in transaction BP. Even when I change the value of lv_synchron in the program LSMOUTILU44 to X so that the function module does not process in the background, I still cannot enter the function module.
The error I am getting is of type E02. Some of the mandatory fields are missing. Despite removing all mandatory fields, I am getting this error.
Can anyone throw some light on this issue please.
Regards,
Abdullah Ismail.

Need to know how to check the outbound queue in SAP for data flow into CRM

Hi Specialist's,
I have changed an entry in Customer Master Data in Sap r/3 and this change has come fine to CRM system.I checked the inbound BDOC in CRM ( Trn:SMW01) and it has come fine into CRM system.I am also able to see the affected field in CRM with new value.
I need to know how to check this from SAP side i.e. I have checked the outbound IDOC list (WE02) but could not find the record.
Is there any other way in SAP that i can check?
Also please let me know if there is any other way except IDOC in SAP to send data from R/3 to CRM?
Usefull answers will definitely be rewarded with points .
Thanks,
Abhinav.

Hi Abhinav,
There are no IDOCs generated in R/3 for replication. R/3 system calls BAPI and Function modules remotely on CRM system which are part of the Adaptors provided for middleware.
Try to deregister the outbound queues in R/3 (Transaction SMQS) and see if you get an entry in the Outbound Queue (Transaction SMQ1). I have not tried this.
If you don't get any entry in the outbound queue then definitely there would be some FM at R/3 end which would be calling CRM system remotely.
<b>Reward points if it helps.</b>
Regards,
Amit Mishra

Impact of inbound and outbound queue

Hi,
I have created the service request in CRM and replicated to r/3, what is the impact on inbound and outbound queue of R/3 and CRM server.
Thanks in advance

Hi
if the mb doc is passed to R3 ok if not you can come to know in smw01 if it gets bounced to crm you need to check for error analysis why bounced, if it get posted R3 inbound queue to r3 is succefull if get bounced back to crm the out bound of crm is failed then depending up on error analysis you should proceed in order to proceed further how to push the transaction to r3 by clearing the middlle ware struck up
CRM Impact is : succefully sent to r3 using mb docs by out bound quue
R3 : if gets bounced in bound quueue is failed to receive the CRM's out bound so you need to rectify in CRM only.
Reward for useful
Venkat

Outbound Queue stacking up for old destination

Hi Gurus,
I am implementing APO in a client and since the native integration (CIF) uses the same RFC structure as BW I need to keep an eye on BW processes as well.
The problem here is that they´ve migrated to BW7, killing the old 3.5 but leaving the logical system registered.
Now what is happening is that I found >4million queues in SMQ1 to this nowhere destination, which kills my CIF performance.
We´ve started to clean this garbage but the stack keeps adding up from regular goods movement transactions. The BASIS and BW team is not helping much so:
I need to find where I set the relationship between theses transactions and the destination so it does not go to the outbound queue.
thanks for the help!

Hi Anand,
Please go to SMQ1 and in qname enter cf* and then execute.
In the error screen press F8 and then select all PPM related queues and delete.
After that run IM after correction and do run CCR report for the reconcilation by tcode :/SAPAPO/CCR .
Manish

Help out for Inbound & Outbound queue

Similar Messages

Maybe you are looking for