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.

Similar Messages

Entry Channel setup for multiple company codes

Hello,
I have a question regarding the entry channel setup (for external requirements in the Plan-Driven Procurement scenario)
In previous implementations, I 've created an entry channel below each company code (as the documentation says it should be). Now, for each entry channel, there was a EBP user assigned, which corresponded to an RFC entry in the backend system (I was connecting EBP to multiple backend systems)
Now, what should I do in the following scenario?:
1. SRM is only connected to one backend system
2. There are 50 company codes
Does that mean I have to create 50 users (for each channel) plus 50 RFC connections in the R/3 system (each with a different user in the backend system), pointing to the same SRM system?
I was thinking of creating an Org iD in the SRM structure at the top (which would be the entry channel), assign only ONE user to it and then fill attribute BUK with all the company codes. However, I don't know if this will work, because the external requirement process might need the company code defined in the "Function" tab... =/
Any help would be greatly appreciated.
Regards,
Gilberto.

Hi Proyecto Genesis,
I am also configuring the Entry channel (org unit) for multiple company codes.
I tried your logic of defining the entry channel outside company code level. Assigned the BUK attribute and extended attribute for plants and storage locations.
Also in my case the local Pur org and Pur group is defined outside the company code. Is it correct?
However the system fails to transfer the external requisition to SRM.
SLG1 displays following error message.
"No address found for partner function type Ship-To Address"
So if I move the Entry channel (org unit) under any one company code level then the external requisitions are transferred correctly to SRM.
But then the issue is the requirements are not transferred with the backend Pur Org and Pur grp. Instead they are transferred to the Pur Org and Pur grp of the company code under which the entry channel is defined.
Can you please share how do we need to define the entry channel, local pur org and pur grp for multiple company codes scenario, so that the ECC requisitions are transferred with the correct company code, pur org and pur grp to SRM?
Or do we need to define Entry channel for each company code and RFC user actually mapping the same backend system?
Please guide.
Regards,
Sandeep

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

ALE - WF Setup for Inbound IDoc

Hi All,
I did ALE - WF setup for IDoc error notifications. If sender port is SAP then it works fine. But if I take port as tRFC then I am unable to receive any Inbound application errors.
Any suggestion for tRFC port? Do I need to do configuration differently?
Thanks in advance!
Regards,
Supriya

Hi All,
I did ALE - WF setup for IDoc error notifications. If sender port is SAP then it works fine. But if I take port as tRFC then I am unable to receive any Inbound application errors.
Any suggestion for tRFC port? Do I need to do configuration differently?
Thanks in advance!
Regards,
Supriya

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

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.

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.

E-commerce gateway setup for PO Outbound

I am trying to configure E-commerce gateway in R12.1.1.
I have completed Trading partner setup.( As per the Implementation guide)
While i am trying to export a PO using - OUT: Purchase Order (850/ORDERS) program i am getting a blank file.
Would appriciate some help on this. I have detailed log available as well but that's too big to be pasted here so just a excerpt from that log is given below
Time Taken 0 seconds
Enter ECE_EXTRACT_UTILS_PUB.FIND_POS->18-NOV-2010 19:06:27
p_in_text: ==>SHIPMENT_NUMBER
p_pos: ==>1
Exit ECE_EXTRACT_UTILS_PUB.FIND_POS->18-NOV-2010 19:06:27
Time Taken 0 seconds
Enter ECE_FLATFILE_PVT.Find_pos->18-NOV-2010 19:06:27
Search text : ==>SHIP_TO_CUSTOMER_NAME
nColumn_count : ==>101
Program Error: PL/SQL position not found for cIn_string.
Program level POOB-10-1428: Please check the log file, correct the problem, and try again.
SQL error message ORA-20001: .
Program level POO-10-1040: Please check the log file, correct the problem, and try again.
SQL error message ORA-20001: .
End of log messages from FND_FILE
---------------------------------------------------------------------------

Welcome to the forums !
Pl post details of OS, database and EBS versions.
Pl see if MOS Doc 393035.1 (ECEPOO and ECEPOCO Errors - PL/SQL cIn_string ORA-20001) can help
HTH
Srini

Wrap-up time for manual outbound calls (UCCX)

Is it possible to configure the wrap-up time for the manual outbound calls in UCCX? I think, this option only exists in CSQ, which is of course meant for the inbound calls. Any thoughts or any workaround to make this work?
Requirement- Once a manual outbound call is hung up, agent's state should be switched to WORK READY as per the wrap-up timer setting.
Thanks.

Dear experts,
I look forward to hear from you if you have anything to offer. Wrap-up TIME to be setup for manual outbound calls in UCCX.
Thanks,
Piyush

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

How does B2B Adapter for Inbound operation for SOA Composite works

Hai,
I am new to B2B. can any one share samples or links or doc's on B2B Adapter for inbound operation (receive)?
Can any one share B2B inbound channel configuration ?

1. How does the above can be achieved using JMS protocol?Where would you like to pitch-in JMS? You want to receive inbound message at B2B over JMS or between SOA and B2B, you want to use JMS?
For receiving inbound message at B2B over JMS, please create a non-internal listening channel at B2B. Make sure to set JMS headers -
http://docs.oracle.com/cd/E23943_01/user.1111/e10229/app_interface.htm#CACDFEAE
For using JMS between, SOA and B2B, create a JMS channel in Host TP profile and add it in the inbound agreement (for inbound scenario). For outbound scenario, create an internal listening channel and make sure that from back-end, headers mentioned on above link, are being set.
2. Will SOA Composite having B2B Adapter receive operation has first operation can get triggered automatically or not as soon as EDI----->XML message is found?Yes, it can be triggered. Provided the steps in your another thread.
3. will B2B Adapter receive operation in SOA Composite will take EDI--------> xml msg as opaque?No, if while modelling B2B adapter, you selected a doc-def otherwise yes.
Regards,
Anuj

What is the b2b setup for identifying TP names from file name in Inbound tx

Hi,
I am using B2B 11g version and documents of type ANSI-X12. I am working for Inbound Transaction and using Generic File protocol in Listening channel.
File format is : %FROM_PARTY%_%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.dat
How can i make B2B to identify Trading partner names from the file name once the remote trading partner put the file in the specified path with the specified format "%FROM_PARTY%_%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.dat" mentioned in the delivery channel.
Now B2B is identifying Trading partner names from the Interchange Sender ID(ISA06) and Interchange Reciever ID(ISA08) of the ISA Segment. Please help me , how to make B2B to identify the trading partner names from the file name instead of from identifiers coming in ISA Segment.
Thanks,
Sridhar Rachumallu

Hi Anuj,
1)Now i am giving the file name for inbound documents in the format of "%FROM_PARTY%_<UniqueNumber/Timestamp>.dat" . But still B2B Identifying the TPNames at runtime from the ISA Segment elements ISA06 & ISA08 element values. I want to make B2B to identify the TPNames at run time from the file name instead of from ISA Segments.
Please tell me how can i do these?
2) I am giving exact Remote Trading partner Default Identifier Type 'NAME' value for "%FROM_PARTY% in the file format and i want B2B to identify the TP name at runtime based on the value of "%FROM_PARTY%" . If the value of "%FROM_PARTY%"is matching with any one of the Trading partner Default Identifier Type 'NAME' value than it should go for furthur else B2B should through error as " the TP name unable to found".
3) Please tell me how B2B Identify trading partners at runtime in the business case given below
- Inbound Transaction from remote TP to Host TP
- Document protocol is 'ANSI-X12'
- Listening channel protocol is 'Generic File'
This is very urgent.. Please give the reply As soon as possible.
Thanks,
Sridhar.rachumallu
Edited by: [email protected] on Jun 9, 2010 12:45 AM
Edited by: [email protected] on Jun 9, 2010 1:01 AM

Seeburger inbound/outbound mapping options with AS2 adapter

Hi Gurus,
This is the first time that i am handling Seeburger adapters(AS2 adapter).
We have the following issue.
We are using AS2 adapter from Seeburger for communicating with Partners (inbound/outbound).
For some scenarios, the trading partners either sends us a flat/csv file or expects a flat/csv file from PI.
And for these scenarios, we are using the AS2 adapter (for sender or receiver channel configuration) .
Now, the main issue is that we need to convert the flat file to PI-XML format when we receive a flat file from a trading partner or we need to convert from PI-XML format to flat file format when we are sending file to a trading partner.
Since the AS2 adapter does not have a File Content Conversion (Like we have in the File/FTP adapter) mechanism, we need to rely on MessageTransformBean (under AF Modules) to do the conversion for us. However, since this module cannot handle deep structures (nested structures) what other alternatives can we look out for ?
I know we can also go for BIC Mapper which is shipped from Seeburger for EDI to XML and XML to EDI conversions. However in this project, we just need XML to flat file/CSV or Flat File/CSV to XML conversions and hence we want to abstain from buying a license for BIC mapper.
Please let me know what other options can we try in this case.
Does Seeburger has anything specific to do the conversions from XML to flat file or flat file to XML (and not the whole BIC mapper tool).
Regards, Gaurav.

Does Seeburger has anything specific to do the conversions from XML to flat file or flat file to XML (and not the whole BIC mapper tool).
No. Seeburger doesn't provide any such tool/option.
Please let me know what other options can we try in this case.
As per the detail you have provided, you don't have any standard option left. You have to either develop your own adapter module or you can pass the payload directly to mapping and then perform Java mapping on it. You have option of using Conversion Agent but there must be some license cost for it as well.
Regards,
Prateek

Oracle EBS Inbound/Outbound Interface build using Oracle SOA 11g

Hi SOA Guru's,
I am very much new to SOA 11g, could you guy's help me in understanding "How I can build any Oracle EBS Inbound/Outbound interface using Oracle SOA 11g"
It will be great if anybody explain me with any example script/screen shot/document.
Thanks in advance.
Regards
Pankaj

I don't have any experience with ebs, but i assume it works like this.
In the composite editor you will find a list adapters at the right..over here you will also find the oracle applications (ebs) adapter.
This will be the component for you which will communicate with the ebs packages.
you need to drag this adapter on the swim lane, and after that you should create the composite application like the way it's described in the tutorials Oracle supplies, put a mediator component in the middle and expose this interface (drag the line to the left swim line)
Hope it's a bit clear like this ?
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/fod_intro2.htm
this should make a few things clear too

Oracle EDI Inbound & Outbound setup docs R12.1.3 overview

Hi Gurus,
Please share with me setup docs for Oracle EDI Inbound & Outbound . If possible Pros and Cons of EDI .. as we're suggesting this for one of our esteemed client in UK.
Also let me know below are possible are not with Oracle EDI functionality :
Plug in custom solution or logic to dervice item Pricing, Item Cross Reference and Unit of Measure while creating Sales order in EBS ?
Many thanks,
Mahe

Duplicate - Oracle EDI Inbound and Outbound setup docs R12.1.3

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

Similar Messages

Maybe you are looking for