SCM Inbound Interfaces for 11i

Is there any SCM Inbound Interface for 11i for external non-Oracle systems to place a requsition or purchase order? if so, what protocol does it use and is this protocol standard for a 11i install?
This interface would be from PeopleSoft 8.47 not currently setup up to use BPEL.
Thanks in Advance

Hi,
As I understand, you have to map incoming message to same message structure of outbound side and then send it to two different receivers.
If this is correct, then you need not perform two message mappings. You need to design the scenario like a normal scenario in Integration Repository. However, in Integration Directory, you would need additional configuration to have two receivers for same message. This would be as follows:
1. Business System for receiver
2. CC for receiver
3. One Receiver Determination with two receivers configured. However, no condition specified for them.
4. Two interface determinations, one for each receiver.
5. Receiver agreements.
This configuration should solve your problem.
Thanks,
Bhavish

Similar Messages

Need information on how to create Idoc Inbound Interfaces for Business Sys

Hi,
I'm losing it.
Can anyone point me to some documentation or an example of how to create inbound interfaces for Business Systems in PI 7.1.
Here's the scenario
I'm working on a B2B integration process which sends inbound idocs to an ECC 6.0 system.
I've created the Business System communication component but under the Inbound Interfaces it is blank.
I want to have MBGMCR.MGBMCR03 as an inbound interface.
But I forget how to get it there.
For Business components you can just add the inbound interface.
I've already defined the Business System in the SLD pointed it to the correct Tech System, imported the idoc definitions in the Enterprise Service Builder and set up IDX1, IDX2 to ensure the metadata exists in PI.
But for Business systems the hep says that it's got to come from the SLD.
Outbound/Inbound Interfaces
For each business system, the interfaces that are installed on the business system are also entered in the SLD. These interfaces are displayed in this frame. You cannot add any other interfaces.
I know I've done this before, but I can't remember how.
Cheers,
John

Hi John ,
Please have a look at the following links which might be of help to you
PI 7.1 IDocs interfaces act as operations
http://www.sdn.sap.com/irj/scn/weblogs;?blog=/pub/wlg/7933
/people/peter.gutsche/blog/2008/10/27/what146s-new-in-sap-netweaver-pi-71
There is a section in the following link on IDOC , have a look at the links in that section
https://wiki.sdn.sap.com/wiki/display/XI/ImportantBlogsand+Notes
Best Regards

Inbound Interface for Accepting Bank Statement Through EDI

Hi All ,
Pls Help me out to complete this Scenerio with u r Ideas and Inputs .
Inbound Interface for Accepting Bank Statement Through EDI.
Rgds
Rafi .

Hi,
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training

SAR inbound interface for SUS

Hello,
Can anyone tell me what inbound interface the SAR (schedule agreement release) uses? I am unable to find the inbound interface in SPROXY.
Also, any good links for implementing Schedule Agreements in SUS.
Thanks,
Matt

there is no seperate inbound interface for SAR , the purchase order inbound interface is used for creating scheduled agreement release in SUS.
only thing that differentiates between PO and SAR in SUS is the header description, descriptuon will have DELINS For SAR.
and both the documents use the function module BBP_API_SUSPO_CRT
set subtype (SR) for SA releases for SUS-MM scenario
IF ls_header_v_u-description EQ 'DELINS'.
also note that the object type for both the PO and SAR in SUS is the same and is 'BUS2230'.

Can anyone help regarding an inbound interface for SAP HCM

Hi guys,
In my recent project I have a inbound interface requirement like the following:
1. The HCM solution system receives the objects on loan information from the non-SAP SCM source system;
2. The information, after certain validation, needs to be updated into the SAP HCM solution on loan Infotype 0040 with asset details.
4. If invalid, HCM solution should not be updated and a log needs to be generated.
The data needs flows through SAP PI. I could not find any IDoc type that can be used here but I found an ES http://esworkplace.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?packageid=DE0426DD9B0249F19515001A64D3F462&id=227F23C7EFA911DA2B24000F20DAC9EF. I am not sure how to progress on this. I would really appreciate your help.
Kind regards
Nilay

You may find this document very useful for SAP HR integration using Idocs
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=85884992

Inbound interface for payroll

Hi All,
I have been asked to build a interface where in data is loaded in SAP in IT 0221 from a legacy input file that is recieved. A batch process has to rum to load this data in fields like wage type, amount, tax authority, check date pay id and OC reason of infotype 0221 with subtype Manual payment.
As a part of this inbound interface reports are genrated which segregate information in file by the subsidary code and grant type fields of legacy input file.
PLZ Suggest what approch should be followed BDC can be helpful to load the load the data????
Plz provide with any useful link or some sample code that could be applicable.
Satifactory answers would be highly rewarded.
Thanks,
Naveen

Dear Naveen,
You can use BDC or standard FM's like HR_INFOTYPE_OPERATION
or HR_MAINTAIN_MASTERDATA.
Check in the forum there are lot of threads which have sample coding on this.
Hope this helps.
Kindly reward if useful.
Regards & Thanks,
Darshan Mulmule

Define Inbound Interface for Interface Mapping with Java functions

Hi,
we are developing an R/3-XI-ITK-SBO system. We realized our SOAP component as custom java functions and we installed it on ITK.
We need to import and configure these functionality in XI because we need to reference to it when we define the Message Interface and the Interface Mapping in Integration Builder Design.
Someone is able to tell us how we can import and configure these java function or definition in XI?
Thanks in advance.
Best regards.

Hi,
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training

Missing Inbound Interface under Edit Service for Business System

Hello All,
I have to configure a Scenario at Integration Directory. Import from IR already done.
When i try to configure a Service under Party\Service\Business System I am not able to find the special IDoc type (here) PROJECT:PROJECT01 under register card "Receiver" (Inbound Interfaces) for the SLD defined Business System.
How can i add the IDoc type here?
Many thanks in advanced?
Regards,
Jochen

Hi,
please let me explain more in detail. All answer not really facing my problem.
At Integration Directory i want to create a Business System Service for a external incoming connection.
When i try to create under the Scenario e.g. "IS_WBSElements" the Service " BTS_Partner" under \Party\<partern>\Service\Business System\ at Display Service i couldn't find the IDoc Type PROJECT.PROJECT01. This will displayed at Display Services under Point Business System "Receiver" card (Inbound Interfaces"). There is a list of some Inbound Interfaces displayed with column Name, Namespace and Software Component Version.
When try to add a different Business System under Party\Service e.g. BTS_CCM i get much more Inbound Interfaces displayed incl. PROJECT.PROJECT01.
Perhaps there is a relation between Inbound Interface and the Business System?!
Many thanks in advance!
Regards,
Jochen

Tax columns to be populated in ra_interface_lines_all table in Inbound Interface???

Hi All,
We are upgrading EBS from 11i instance to R 12.1.3. There is inbound interface for Recevibles transactions which fetches data from a data file and imports invoices after validation.
In 11i, tax_code column in ra_interface_lines_all was populated to import the tax details. But, in R12 tax_code column is not used. Can anyone tell me which columns we need to populate in ra_interface_lines_all table for tax details, i can see there are many tax related columns. I am deriving tax details from zx_rates_b table.
Which column should be used from this table as a input in tax_code(or other column) in ra_interface_lines_all.??
Thanks
Swapnil K.

Hi Swapnil,
For Tax, value to be taken from ZX_TAXES_B.TAX
For TAX_STATUS_CODE, value to be taken from ZX_STATUS_B.TAX_STATUS_CODE
For TAX_RATE_CODE, value to be taken from ZX_RATES_B. TAX_RATE_CODE
For further details on the mapping refer to the oracle documentation from below reference ...
Description and Usage of Fields in RA_INTERFACE_LINES Table (Doc ID 1195997.1)
Regards,
Ivruksha

Receiver Business System Connot find Inbound Interface - IDoc to File

Hi Everyone,
I am doing IDoc to File Scenario.....Idoc got triggered from SAP system and successfully posted to SAP PI.
Now when I check in T-Code IDX5 in PI, I got one message. When I double click that I am getting following error:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also When I am selecting Receiving Inbound interface for Receiver system, I am not getting any interface by default.
Please help me out.
Thanks & Regards,
Sudheer

Hi everyone,
Thanks for your quick responses.
Actually I am doing IDoc to File Scenario from blog which consists of Conditional Receiver Determination
"SNDPFC"
Here is the Explanation given in that blog:
In most instances, a new Receiver Determination would be created. However, given that in this scenario the combination of the sender service (i.e. u201CGL1u201D) and interface (i.e. u201CMATMAS.MATMAS04u201D) will be used by every student, each student will instead be adding their receiver service to an existing Receiver Determination
11. In the Condition column on that same line, left click on the question mark help icon
12. In the following Condition Editor pop-up window, left click on the help icon in the u201CLeft Operandu201D field
13. In the following Expression Editor pop-up window, select the u201CContext Objectu201D radio button
14. Use the drop drown to locate and select the u201CSNDPFCu201D field and u201COKu201D
15. Back in the Expression Editor, leave the u201C=u201D Operand as is
16. Enter your group number in the u201CRight Operandu201D and u201COKu201D
17. u201CSaveu201D and validate your u201CConfigured Receiversu201D as seen below:
I did not understood this Conditional RD.
Apart from this all configuration are correct.
Thanks,
Sudheer

Idoc inbound interface

Hi experts,
I am working on inbound interface for MATMAS04. I am using BAPI_MASTER_SAVEDATA to create material.
Now Can anyone suggest me any inbound function module that returns IDOC number. I am getting data in form of File. EDI_DATA_INCOMING doesnot return idoc number.
Thanks and regards
Neha Kapoor

hi neha,
Creating a Function Module (Direct Inbound Processing)
This describes how to create a function module which is identified by the IDoc Interface using a new process code and called from ALE (field TBD52-FUNCNAME). Direct inbound processing using a function module (not using a workflow) always includes the ALE layer. This setting (processing with function module and ALE layer) is identified by the value 6 in the field TEDE2-EDIVRS, which is read by the function module IDOC_START_INBOUND. IDOC_START_INBOUND then calls ALE.
Example
FUNCTION IDOC_INPUT_TESTER.
""Globale Schnittstelle:
*" IMPORTING
*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*" VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*" VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*" VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*" VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*" VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*" IDOC_CONTRL STRUCTURE EDIDC OPTIONAL
*" IDOC_DATA STRUCTURE EDIDD
*" IDOC_STATUS STRUCTURE BDIDOCSTAT
*" RETURN_VARIABLES STRUCTURE BDWFRETVAR
*" SERIALIZATION_INFO STRUCTURE BDI_SER
initialize SET/GET Parameter and internal tables
PERFORM INITIALIZE_ORGANIZATIONAL_DATA.
Move IDOC to internal tables of application
PERFORM READ_IDOC_TESTER.
call transaction Order Entry VA01
PERFORM CALL_VA01_IDOC_ORDERS USING ERRORCODE.
set status value
perform write_status_record using errorcode.
return values of function module
PERFORM RETURN_VARIABLES_FILL USING ERRORCODE.
ENDFUNCTION.
FORM INITIALIZE_ORGANIZATIONAL_DATA.
initialize SET/GET parameters
SET PARAMETER ID 'VKO' FIELD SPACE.
SET PARAMETER ID 'VTW' FIELD SPACE.
SET PARAMETER ID 'SPA' FIELD SPACE.
SET PARAMETER ID 'VKB' FIELD SPACE.
SET PARAMETER ID 'VKG' FIELD SPACE.
initialize internal tables
REFRESH BDCDATA.
CLEAR BDCDATA.
CLEAR BELEGNUMMER.
CLEAR ERRTAB.
REFRESH ERRTAB.
REFRESH XBDCMSGCOLL.
CLEAR XBDCMSGCOLL.
ENDFORM. " INITIALIZE_ORGANIZATIONAL_DATA
FORM READ_IDOC_TESTER.
PERFORM INITIALIZE_IDOC.
LOOP AT IDOC_DATA
WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
header data
WHEN 'E1HEAD'.
MOVE IDOC_DATA-SDATA TO E1HEAD.
PERFORM PROCESS_SEGMENT_E1HEAD.
position data
WHEN 'E1ITEM'.
MOVE IDOC_DATA-SDATA TO E1ITEM.
PERFORM PROCESS_SEGMENT_E1ITEM.
ENDCASE.
ENDLOOP.
only when there were one or more items
CHECK FIRST NE 'X'.
APPEND XVBAP. "last one
ENDFORM. " READ_IDOC_TESTER
FORM INITIALIZE_IDOC.
CLEAR XVBAK.
REFRESH XVBAP.
CLEAR XVBAP.
POSNR = 0.
FIRST = 'X'.
ENDFORM. " INITIALIZE_IDOC
FORM PROCESS_SEGMENT_E1HEAD.
requested date of delivery
WLDAT = E1HEAD-WLDAT.
delivery date
XVBAK-BSTDK = E1HEAD-BSTDK.
customer number
XVBAK-KUNNR = E1HEAD-AUGEB.
order number
XVBAK-BSTNK = E1HEAD-BELNR.
division
XVBAK-SPART = E1HEAD-SPART.
distribution channel
XVBAK-VTWEG = E1HEAD-VTWEG.
sales organization
XVBAK-VKORG = E1HEAD-VKORG.
order type
XVBAK-AUART = E1HEAD-AUART.
do not fill incoterms (inco1, inco2)
customer function
CALL CUSTOMER-FUNCTION '001'
EXPORTING
PI_VBAK621 = XVBAK
IMPORTING
PE_VBAK621 = XVBAK
TABLES
PT_IDOC_DATA_RECORDS = IDOC_DATA.
ENDFORM. " PROCESS_SEGMENT_E1HEAD
FORM PROCESS_SEGMENT_E1ITEM.
position number
XVBAP-POSNR = XVBAP-POSNR + 1.
amount
XVBAP-WMENG = E1ITEM-MENGE.
unit
CALL FUNCTION 'ISO_TO_SAP_MEASURE_UNIT_CODE'
EXPORTING
ISO_CODE = E1ITEM-BMEINH
IMPORTING
SAP_CODE = XVBAP-VRKME
EXCEPTIONS
OTHERS = 0.
material number
XVBAP-MATNR = E1ITEM-LMATNR.
CALL CUSTOMER-FUNCTION '002'
EXPORTING
PI_VBAP621 = XVBAP
IMPORTING
PE_VBAP621 = XVBAP
TABLES
PT_IDOC_DATA_RECORDS = IDOC_DATA.
APPEND XVBAP.
ENDFORM. " PROCESS_SEGMENT_E1ITEM
FORM CALL_VA01_IDOC_ORDERS USING ERRORCODE.
call transaction first dynpro
PERFORM DYNPRO_START.
call transaction double-line entry
PERFORM DYNPRO_DETAIL2.
incoterms
PERFORM DYNPRO_HEAD_300.
call transaction item datas
PERFORM DYNPRO_POSITION.
PERFORM DYNPRO_SET USING 'BDC_OKCODE' 'SICH'.
determine input method
IF INPUT_METHOD IS INITIAL.
INPUT_METHOD = 'N'.
ENDIF.
call transaction VA01
CALL TRANSACTION 'VA01' USING BDCDATA
MODE INPUT_METHOD
UPDATE 'S'
MESSAGES INTO XBDCMSGCOLL.
errorcode = SY-SUBRC. " remember returncode for status update
ENDFORM. " CALL_VA01_IDOC_ORDERS
form write_status_record using errorcode.
FILL IDOC_STATUS
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IF ERRORCODE = 0.
IDOC_STATUS-STATUS = BELEG_GEBUCHT. "value 53
GET PARAMETER ID 'AUN' FIELD BELEGNUMMER.
IDOC_STATUS-MSGID = 'V1'.
IDOC_STATUS-MSGNO = '311'.
IDOC_STATUS-MSGV1 = 'Terminauftrag'.
IDOC_STATUS-MSGV2 = BELEGNUMMER.
ELSE.
IDOC_STATUS-STATUS = BELEG_NICHT_GEBUCHT. "value 51
IDOC_STATUS-MSGID = SY-MSwGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM.
FORM DYNPRO_START.
PERFORM DYNPRO_NEW USING PROGRAMM_AUFTRAG
DYNPRO-EINSTIEG
CHANGING LAST_DYNPRO.
ordertype
PERFORM DYNPRO_SET USING 'VBAK-AUART' XVBAK-AUART.
sales organization
PERFORM DYNPRO_SET USING 'VBAK-VKORG' XVBAK-VKORG.
Distribution channel
PERFORM DYNPRO_SET USING 'VBAK-VTWEG' XVBAK-VTWEG.
Division
PERFORM DYNPRO_SET USING 'VBAK-SPART' XVBAK-SPART.
Sales office
PERFORM DYNPRO_SET USING 'VBAK-VKBUR' XVBAK-VKBUR.
Sales group
PERFORM DYNPRO_SET USING 'VBAK-VKGRP' XVBAK-VKGRP.
ENDFORM. " DYNPRO_START
FORM DYNPRO_NEW USING PROGNAME
DYNPRONR
CHANGING LAST_DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGNAME.
BDCDATA-DYNPRO = DYNPRONR.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
LAST_DYNPRO = DYNPRONR.
ENDFORM. " DYNPRO_NEW
FORM DYNPRO_SET USING FELDNAME
FELDINHALT.
CLEAR BDCDATA.
CHECK FELDINHALT NE SPACE.
dynpro field name
BDCDATA-FNAM = FELDNAME.
contents
BDCDATA-FVAL = FELDINHALT.
APPEND BDCDATA.
ENDFORM. " DYNPRO_SET
FORM DYNPRO_DETAIL2.
okcode
PERFORM DYNPRO_SET USING 'BDC_OKCODE' PANEL-UER2.
fix dynpro number 4001
PERFORM DYNPRO_NEW USING PROGRAMM_AUFTRAG
'4001'
CHANGING LAST_DYNPRO.
order party
PERFORM DYNPRO_SET USING 'KUAGV-KUNNR' XVBAK-KUNNR.
purchase order number
PERFORM DYNPRO_SET USING 'VBKD-BSTKD' XVBAK-BSTNK.
requested delivery date
PERFORM DYNPRO_DATE_SET USING 'VBKD-BSTDK' XVBAK-BSTDK.
purchase order date
PERFORM DYNPRO_DATE_SET USING 'RV45A-KETDAT' WLDAT.
ENDFORM. " DYNPRO_DETAIL2
FORM DYNPRO_DATE_SET USING FELDNAME
FELDINHALT.
DATA: DATE TYPE D.
CLEAR BDCDATA.
CHECK FELDINHALT NE SPACE.
BDCDATA-FNAM = FELDNAME.
WRITE FELDINHALT TO DATE.
BDCDATA-FVAL = DATE.
APPEND BDCDATA.
ENDFORM. " DYNPRO_DATE_SET
FORM DYNPRO_HEAD_300.
PERFORM DYNPRO_SET USING 'BDC_OKCODE' PANEL-KKAU.
incoterms part 1
IF NOT XVBAK-INCO1 IS INITIAL.
PERFORM DYNPRO_SET USING 'VBKD-INCO1' XVBAK-INCO1.
ENDIF.
incoterms part 2
IF NOT XVBAK-INCO2 IS INITIAL.
PERFORM DYNPRO_SET USING 'VBKD-INCO2' XVBAK-INCO2.
ENDIF.
PERFORM DYNPRO_SET USING 'BDC_OKCODE' 'BACK'.
ENDFORM. " DYNPRO_HEAD_300
FORM DYNPRO_POSITION.
LOOP AT XVBAP.
dynpro item double line entry
PERFORM DYNPRO_SET USING 'BDC_OKCODE' 'UER2'.
IF XVBAP-POSNR = 1.
material number
PERFORM DYNPRO_SET USING 'VBAP-MATNR(01)' XVBAP-MATNR.
order quantity
PERFORM DYNPRO_SET USING 'RV45A-KWMENG(01)' XVBAP-WMENG.
desired delivery date
PERFORM DYNPRO_DATE_SET USING 'RV45A-ETDAT(1)' WLDAT.
sales unit
PERFORM DYNPRO_SET USING 'VBAP-VRKME(1)' XVBAP-VRKME.
ELSE.
PERFORM DYNPRO_SET USING 'BDC_OKCODE' 'POAN'.
material number
PERFORM DYNPRO_SET USING 'VBAP-MATNR(02)' XVBAP-MATNR.
order quantity
PERFORM DYNPRO_SET USING 'RV45A-KWMENG(02)' XVBAP-WMENG.
desired delivery date
PERFORM DYNPRO_DATE_SET USING 'RV45A-ETDAT(02)' WLDAT.
sales unit
PERFORM DYNPRO_SET USING 'VBAP-VRKME(02)' XVBAP-VRKME.
ENDIF.
ENDLOOP.
ENDFORM. " DYNPRO_POSITION
FORM RETURN_VARIABLES_FILL USING ERRORCODE.
allocate IDOC numbers to Workflow output parameters
IF MASS_PROCESSING <> SPACE.
IF ERRORCODE = 0.
RETURN_VARIABLES-WF_PARAM = PID.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
RETURN_VARIABLES-WF_PARAM = APO.
RETURN_VARIABLES-DOC_NUMBER = BELEGNUMMER.
APPEND RETURN_VARIABLES.
WORKFLOW_RESULT = C_WF_RESULT_OK.
ELSE.
RETURN_VARIABLES-WF_PARAM = EID.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
WORKFLOW_RESULT = C_WF_RESULT_ERROR.
ENDIF.
ELSE.
IF ERRORCODE = 0.
RETURN_VARIABLES-WF_PARAM = APE.
RETURN_VARIABLES-DOC_NUMBER = BELEGNUMMER.
APPEND RETURN_VARIABLES.
WORKFLOW_RESULT = C_WF_RESULT_OK.
ELSE.
WORKFLOW_RESULT = C_WF_RESULT_ERROR.
ENDIF.
ENDIF.
ENDFORM. " RETURN_VARIABLES_FILL
Globale Daten von IDOC_INPUT_TESTER
TABLES: E1HEAD, E1ITEM.
DATA: BEGIN OF BDCDATA OCCURS 500.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BEGIN OF XVBAK. "Kopfdaten
INCLUDE STRUCTURE VBAK621.
DATA: END OF XVBAK.
DATA: BEGIN OF XVBAP OCCURS 50. "Position
INCLUDE STRUCTURE VBAP.
DATA: WMENG(18) TYPE C.
DATA: LFDAT LIKE VBAP-ABDAT.
DATA: KSCHL LIKE KOMV-KSCHL.
DATA: KBTRG(16) TYPE C.
DATA: KSCHL_NETWR LIKE KOMV-KSCHL.
DATA: KBTRG_NETWR(16) TYPE C.
DATA: INCO1 LIKE VBKD-INCO1.
DATA: INCO2 LIKE VBKD-INCO2.
DATA: YANTLF(1) TYPE C.
DATA: PRSDT LIKE VBKD-PRSDT.
DATA: HPRSFD LIKE TVAP-PRSFD.
DATA: END OF XVBAP.
DATA: BEGIN OF DYNPRO,
EINSTIEG LIKE T185V-DYNNR VALUE 101,
KKAU LIKE T185V-DYNNR,
UER2 LIKE T185V-DYNNR,
KBES LIKE T185V-DYNNR,
ERF1 LIKE T185V-DYNNR,
PBES LIKE T185V-DYNNR,
PKAU LIKE T185V-DYNNR,
PEIN LIKE T185V-DYNNR,
EID1 LIKE T185V-DYNNR,
POPO LIKE T185V-DYNNR,
EIPO LIKE T185V-DYNNR,
KPAR LIKE T185V-DYNNR,
PSDE LIKE T185V-DYNNR,
PPAR LIKE T185V-DYNNR,
KDE1 LIKE T185V-DYNNR,
KDE2 LIKE T185V-DYNNR,
PDE1 LIKE T185V-DYNNR,
PDE2 LIKE T185V-DYNNR,
PKON LIKE T185V-DYNNR,
END OF DYNPRO.
DATA: BEGIN OF PANEL,
KKAU LIKE T185V-PANEL VALUE 'KKAU',
UER2 LIKE T185V-PANEL VALUE 'UER2',
KBES LIKE T185V-PANEL VALUE 'KBES',
ERF1 LIKE T185V-PANEL VALUE 'ERF1',
PBES LIKE T185V-PANEL VALUE 'PBES',
PKAU LIKE T185V-PANEL VALUE 'PKAU',
PEIN LIKE T185V-PANEL VALUE 'PEIN',
EID1 LIKE T185V-PANEL VALUE 'EID1',
EIAN LIKE T185V-PANEL VALUE 'EIAN',
POPO LIKE T185V-PANEL VALUE 'POPO',
EIPO LIKE T185V-PANEL VALUE 'EIPO',
KPAR LIKE T185V-PANEL VALUE 'KPAR',
PSDE LIKE T185V-PANEL VALUE 'PSDE',
POAN LIKE T185V-PANEL VALUE 'POAN',
PPAR LIKE T185V-PANEL VALUE 'PPAR',
KDE1 LIKE T185V-PANEL VALUE 'KDE1',
KDE2 LIKE T185V-PANEL VALUE 'KDE2',
PDE1 LIKE T185V-PANEL VALUE 'PDE1',
PDE2 LIKE T185V-PANEL VALUE 'PDE2',
PKON LIKE T185V-PANEL VALUE 'PKON',
KOAN LIKE T185V-PANEL VALUE 'KOAN',
END OF PANEL.
DATA: BEGIN OF ERRTAB OCCURS 20,
TRANS LIKE TSTC-TCODE,
ARBGB LIKE T100-ARBGB,
CLASS(1) TYPE C,
MSGNR LIKE T100-MSGNR,
TEXT LIKE T100-TEXT,
TEXT(123) TYPE C,
MSGV1 LIKE SY-MSGV1,
MSGV2 LIKE SY-MSGV2,
MSGV3 LIKE SY-MSGV3,
MSGV4 LIKE SY-MSGV4,
END OF ERRTAB.
*---- Hilfsfelder -
DATA: PROGRAMM_AUFTRAG LIKE T185V-AGIDV VALUE 'SAPMV45A'.
DATA: LAST_DYNPRO LIKE T185V-DYNNR,
WLDAT LIKE VBAK-BSTDK,
POSNR LIKE VBAP-POSNR,
FIRST(1) TYPE C VALUE 'X'.
DATA: BEGIN OF XBDCMSGCOLL OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF XBDCMSGCOLL.
Terminauftrag ( Auftragsart wird fest gesetzt !)
DATA: BELEGNUMMER LIKE VBAK-VBELN.
DATA: ERRORCODE LIKE SY-SUBRC.
Statuswerte fuer IDOC-Status
DATA: BELEG_NICHT_GEBUCHT LIKE TEDS1-STATUS VALUE '51'.
DATA: BELEG_GEBUCHT LIKE TEDS1-STATUS VALUE '53'.
*- Direktwerte für Return_variables -
data:
eid like bdwfretvar-wf_param value 'Error_IDOCs',
pid like bdwfretvar-wf_param value 'Processed_IDOCs',
apo like bdwfretvar-wf_param value 'Appl_Objects',
ape like bdwfretvar-wf_param value 'Appl_Object'.
*- Direktwerte für Workflow_Result -
DATA: C_WF_RESULT_ERROR LIKE BDWFAP_PAR-RESULT VALUE '99999'.
DATA: C_WF_RESULT_OK LIKE BDWFAP_PAR-RESULT VALUE '0'.
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f
Plz Reward points if helpfull ...
Regards,
Mandeep.

URGENT - XI to SRM : Interface for 'Request For Quotation'

Hello Guyz!...
I am trying to develop an interface in XI to post 'Request For Quotation' into SRM system. Can anybody help me on this.. Any kind of help is greatly appreciated. Thanks in Advance.

Hi Praveen,
No need to create a new inbound interface for posting the RFQ in SRM. You can use the SAP predefined inbound interface "RequestForQuotationResponse_CreateOrChange_In" present in the name space "http://sap.com/xi/EBP". Also it will have a corresponding proxy in SRM side which will call a stard function module.
All you need to do here is create DT, MT, MI required for source and do the mapping.
Regards,
Jai Shankar.

Vendor Master Inbound Interface

Hi All,
Is there a FM that can be used in an inbound interface for the vendor master creation?
We are using an extension of CREMAS05 basic type.
Thanks in advance.

Hi,
Thanks for the reply, but the FM IDOC_INPUT_CREDITOR calls FM ERP_IDOC_INPUT_CREDITOR and it is checks for IDoc types. If the IDoc type is not CREMAS01 to CREMAS05 it raises an exception.
As we are using an extension of CREMAS05, the FM gives exception.
So we are looking for some other FM or BAPI.
We were not able to find any BAPI for Vendor master creation.
Any other solution?
Thanks in advance.

Can any1 send me the detail of inbound interface

I have to do inbound interface for shipment. can anyone give me the detail.how to start and how to do with BDC programming.I am new to interface.

Hi,
Check these links.
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
http://www.sappoint.com/abap/bdcrec.pdf
http://www.sappoint.com/abap/bdcconcept.pdf
http://www.sap-img.com/bdc.htm
BDC
http://www.sap-img.com/bdc.htm
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
http://www.sappoint.com/abap/bdcconcept.pdf
Difference between Genrate session& Call transaction
Re: Steps in BDC
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
www.sapgenie.com
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
http://www.planetsap.com/bdc_main_page.htm
www.abap4u.com
http://www.sappoint.com/abap/bdcconcept.pdf
Difference between Genrate session& Call transaction
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
http://www.sappoint.com/abap/bdcrec.pdf
http://www.sappoint.com/abap/bdcconcept.pdf
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Re: BDC learning
Reward if useful.
Thanks
Aneesh.

How to connect to third party using PI for outbound and inbound interfaces

Hello,
I have scenarios where I have data coming in from third party EDI subsystem and sent to SAP. And also from SAP to EDI subsystem. We need to send the XMLs to the EDI subsystema nd also receive XMLs.
Can someone please suggest the ways I can connect to EDI subsytem for both Outbound and Inbound interfaces.
Thanks

Hi Prabhu,
EDI file is different from the normal flat or xml file. Hope you understand the difference.
Now if your EDI subsytem has the capability of converting the xml file to edi file viceversa then create and receive the xml file from the EDI subsystem. For the xml file you may use the file adapter as an option.
If it doesnot have the capability then seeburger adapter needs to be used. This is not an inbuilt adapter. So your company needs to purchase it.
Regards,
---Satish

SCM Inbound Interfaces for 11i

Similar Messages

Maybe you are looking for