EDI outbound

I am doing a EDI outbound for purchase order using
message type as ORDERS
Idoc type as ORDERS05
My scenario is as such, a flat file will be having text information and IDOC number and I need to add the outbound idoc with this text information provided in the flatfile for the corresponding IDOC number in the file.
My issue is that how to add information in the file to generated IDOC .

Hi Shreya,
It seems you need to go for an idoc extension.
Extenbd the idoc and populate the extended segments by using the user exits in the outbound function module.
Visit this link for more info:
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Regards,
Ravi

Similar Messages

EDI outbound error

Hi All
we are working on EDI outbound messages and facing the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">APPLICATION_PROGRAM_ERROR</SAP:Code>
<SAP:P1>Z_ABAP_MAPPING_IDOC_TO_FLAT</SAP:P1>
<SAP:P2>SAP-ABAP</SAP:P2>
<SAP:P3>UNCAUGHT_EXCEPTION</SAP:P3>
<SAP:P4>Program Z_ABAP_MAPPING_IDOC_TO_FLAT===CP Include Z_ABAP_MAPPING_IDOC_TO_FLAT===CM001 Line 1</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error in mapping program Z_ABAP_MAPPING_IDOC_TO_FLAT (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
How can i solve this error.
Regards
Ashwin Kumar

HI Ashwin
I think this exception you need to catch it in the ABAP..
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Cheers..
Vasu
<i>** Reward Points if found useful **</i>

EDI Outbound 855 Error Code:AIP-51505 Unable to create outbound file

Hi,
I am facing some issues while processing EDI Outbound 855.
I am getting error in B2B . I have checked ECS and XSD. There is no mismatch
Error description: Extra elements were found in the data file as part of Segment PO1 at guideline position 010.{br}{br}This error was detected at:{br}{tab}Segment Count: 3{br}{tab}Element Position: 5{br}{tab}Characters: 1388 through 1390
Can any one give me some resolution for this one.
Regards,
Rao

Hello Rao,
It appears from your previous post,
1. This issue is there only for one Trading Partner.
2. You have already validated document against XSD and also XSD is generated from the ecs which is getting used, transaction set ecs does not contain envelop details.
Please do the following.
1. Please make sure you have not overridden transaction set ecs as part of operational Capability.
2. Please send us the b2b.log in DEBUG mode along with ecs and payload(XML) which will help us to identify which segment is extra in it.
Rgds, Ramesh

RFC Destination to test EDI outbound process

Hi,
I am configuring RFC Destination. SAP provides a tool to test EDI outbound process even when EDI subsystem is not actually connected. Do you know what the RFC destination settings should be in this scenario? Thank you.

Hi,
Please check this links perhaps they may help.
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/mysap3/sap109.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
Regards,
Ferry Lianto

HELP!!! - EDI Outbound HTTP call failure

Our EDI outbound (HTTPS-OXTA) is failing since Monday in production. We narrowed down the area that might be an issue. This is what we see in the Apache log,
[Tue May 22 01:31:56 2012] [debug] opm_ew.c(469): OPM: EW: Enters opm_ew_broadcast()
[Tue May 22 01:31:56 2012] [debug] opm_ew.c(517): OPM: EW: Broadcasts msg: cmd=Broadcast&<serverName>&8001&1337662614&JServ&DiscoGroup&<server_url>&1&1&0&31490&17001;FormsGroup&<server_url>&1&1&0&31491&18001;OACoreGroup&<server_url>&1&1&0&31489&16001;XmlSvcsGrp&<server_url>&1&1&0&31492&19001
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(291): OPM:hc: Connecting to url: <server_url>:8101/oprocmgr-service
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(314): OPM:hc: Connection to host: <server_url>, port: 8101
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(438): OPM:hc: HTTP Request sent to server: POST /oprocmgr-service<server_url> HTTP/1.1^M
Host: <server_url>^M
Content-Type: application/x-www-form-urlencoded^M
Content-Length: 269^M
cmd=Broadcast&<serverName>&8001&1337662614&JServ&DiscoGroup&<server_url>&1&1&0&31490&17001;FormsGroup&<server_url>&1&1&0&31491&18001;OACoreGroup&<server_url>&1&1&0&31489&16001;XmlSvcsGrp&<server_url>&1&1&0&31492&19001
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(808): OPM:hc: headers[0] is HTTP/1.1 404 Not Found
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(808): OPM:hc: headers[1] is Date: Tue, 22 May 2012 05:31:56 GMT
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(808): OPM:hc: headers[2] is Transfer-Encoding: chunked
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(808): OPM:hc: headers[3] is Content-Type: text/html; charset=iso-8859-1
[Tue May 22 01:31:56 2012] [debug] opm_ew.c(525): OPM: EW: Broadcasts to <server_url> and send result=404
I'm trying to understand the steps of the process. Does "HTTP/1.1 404 Not Found" response to the opm_hc.c(438) call? When I type "<server_url>:8101" in the browser, I get "The webpage cannot be displayed" error. Does this should work?
EDI outbound is routed to proxy and confirmed that call from OTA was never made to proxy. Switched protocol to SMTP and it worked. There is no issue other than HTTP initial call failure. Any help you can give me I'd appreciated.

George great support so far (+5)
Hi Robert
debug ccsip all is very intensive so you should do the following before enabling the debug
service sequence-numbers
service timestamps debug datetime localtime msec
logging buffered 10000000 debug
no logging console
no logging monitor
default logging rate-limit
default logging queue-limit
Then..
<Enable debugs, then test again.>
debug ccsip all
<Enable session capture to txt file in terminal program.> (such as Putty)
then do the ff:
terminal length 0
show logging
++++
What is even more strange is that the call appears to be disconnected from the far end. From the logs below the outbound call leg (45) is where the disconnect is coming from and the "cc_api_call_disconnected" shows this call leg talking to CCAPI..
001858: *Jan 20 13:18:19.102: //45/8B56ECEE8011/CCAPI/cc_api_call_disconnected:
Cause Value=16, Interface=0x3CE6D670, Call Id=45
001859: *Jan 20 13:18:19.102: //45/8B56ECEE8011/CCAPI/cc_api_call_disconnected:
Call Entry(Responsed=TRUE, Cause Value=16, Retry Count=0)
Can you also send a debug voip ccapi onout from the CUBE. we need to check if the call arrives there, though we don't see any INVITE request sent out.

EDI Outbound B2B - Are ST and SE segment values created by B2B

Hi,
I have created a BPEL-B2B outbound EDI sample process
Document is 850
Here BPEL is successfully giving file to B2B
But B2B is erroring with below
Segment ST((N/A)) at guideline position 010 is missing. This segment's standard option is Mandatory.{br}{br}This segment was expected after:{br}{tab}Segment Count: 0{br}{tab}Character: 0
Are ST and SE values to be populated by BPEL (i mean while developing the process should we assign these values) or should B2B create these values
I had assigned some constant values in BPEL, but still I get the above error
Please advise
Thanks
Sachin Sutar

Hi Sachin
You can take a look at the file Acme_850.xml which can be found in B2B under the path ORACLE_HOME\ip\tutorial\X12\runtime
The error could be due to the fact that the hardcoded values you have entered in BPEL are not as per the expected values. The entry in Acme_850.xml are as follows
<Segment-ST>
<Element-143>850</Element-143>
<Element-329>#ControlNumber#</Element-329>
</Segment-ST>
<Segment-SE>
<Element-96>220</Element-96>
<Element-329>#ControlNumber#</Element-329>
</Segment-SE>
Hope this helps.
Thanks,
--Arun

INVOIC EDI OUTBOUND

I'm using message type INVOIC02 for outbound EDI invoices. The invoice has a discount on it but this is not being shown on the IDOC.
I expect to see the data for the following fields but they're not being populated
E1EDS01 SUMID Identifier 020 Total discounts/surcharges
E1EDS01 SUMID Identifier 012 Value qualifying for discount
Can someone let me know what I need to do to include this data in the IDOC.
Many thanks, Mark

You can reprocess the outbound process by using transaction VF31. If you set a breakpoint in function module IDOC_OUTPUT_INVOIC (or something like that) you can see per segment how the fields are filled.
Hans

EDI Outbound Batching Error

Hi All!
We need to batch outbound EDI messages in XML format onto one EDI message. We have used deferred batching that is described in B2B documentation. But we have received the error:
2009.06.30 at 12:25:59:265: Thread-39: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingBatchRequest Invoking PackMessage
2009.06.30 at 12:25:59:281: Thread-39: B2B - (DEBUG) MimePackaging:pack:Enter
2009.06.30 at 12:25:59:296: Thread-39: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage General Exception ERROR
2009.06.30 at 12:25:59:296: Thread-39: B2B - (ERROR) Error -: AIP-50014: General error
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1129)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2355)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
at java.lang.Thread.run(Thread.java:534)
How we can obtain complete information about this error in this case?
Regards.

Hi,
Please refer -
http://www.b2bgurus.com/2009/02/advanced-edi-batching-in-oracle-b2b.html
You may be interested in below links also -
http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TN_012_EDI_OutBound_Batching.pdf
Outbound EDI Message Batching in Integration B2B
Regards,
Anuj
Edited by: Anuj Dwivedi on Jun 30, 2009 5:31 PM

About EDI outbound file name

Hi Anuj,
When I test EDI X12 834 outbound, the file generated is in the format %From_party%_%unique_id%.dat. I am not sure the unique_id is message ID or transaction control number, anyway it is a timestamp unique.
My question is can I specify outbound file name format? File name convention is recently proposed. It is not compliant with the default outbound file name.
Thank you,
Alena
CGI

Hello Sir,
Thank you for reading my thread.
Yes, we have worked on edi 834 and completed a few different transactions with people's support in this forum. Now I am glad to help other people on this.
1. Is HCA Adapter required for EDI 834?
HCA is not required for EDI 834. There are a couple threads discussed this in the forum. You can search Anuj's comments regarding this. See the the link. Oracle B2B is the right solution.
https://forums.oracle.com/thread/2551859
2. Any Healthcare Libraries?
If you are encountering B2B validation problem, you need to install Healthcare Library. But your problem has nothing to do with that. If you don't install the healthcare library, you still can do everything except B2B validation.
3. Any patches
If you are running SOA Suite 11.1.1.6.0, you need to install Health Care Patch to fix B2B validation problem. That is a bug.
If you are running SOA Suite 11.1.1.7.9, you need to install HealthCare Library to fix B2B validation problem. It is the same bug.
4. Any other??
If you are using Oracle B2B, you need to active B2B ui project. It has already deployed on Weblogic server, but you need to activate it. You should be able to access B2B via:
http://localhost:7001/b2bconsole or: http://localhost:7101/b2bconsole
5. Any special care while generating .ecs,xsd,.dazt from doc editor???
I don't need .dazt. You need ecs and xsd for B2B configuration. I disabled a couple validation rules to meet our business requirements. You may not need to.
For your particular problem, as the error message says "it can't find the agreement for the trading partners. B2B needs three information to identify the agreement. The document type (here it is 820 or 834), From TP, and To TP. If these three things meet, then B2B should be able to find it.
Let me know how are you doing after you check these things.
Alena Li

EDI Outbound file trigger not happening automatically.unix script

EDI OUT bound issue:-
We are processing IDOC by using WE19 -> Here we are selecting existing IDOC -> By using pushbutton Start Outbound Processing the IDOC EDI file is creating in directory with file name as:- /abc/xyz/edi/DECVDE_989898.
In the same directory we have unix script file push_idoc_sci.sh is available which sends this EDI file to unix server.This script is working fine when we do manual sending of edi file - there is no issue in the script.
1> We configured the port SAPEDI which sends this EDI file automatically by using this script file. But this is not happening.
WE21 settings:-
Outbound file TAB:- Phycal directory -> /abc/xyz/edi/
                                 Function module: EDI_PATH_CREATE_MESTYP_DOCNUM
Outbound Trigget TAB:-
                                Automatic Start Possible check box checked.
                                RFC destination -- SERVER_EXCE.
                                Directory-- /abc/xyz/edi/
                                Command file -- push_idoc_sci.sh
Inbound file TAB:- Phycal directory -> /abc/xyz/edi/ in
                             FM -- EDI_PATH_CREATE_CLIENT_DOCNUM
2> RFC destination TCP/IP connections:- SERVER_EXEC configured with parameters:
     Application server :- Program: rfcexec.
The Issues is EDI file is creating in applicastion server, but it is not going automatically to unix server as automated process. even we mentoned the script in port defination to send automatically.
Is there any we are missing? any seetings do we need to do extra?
Please let us know.
Thanks in advance.
Sreedhara.

Hi Hi sreedhara gupta
what REDDY said is correct. Still you if you want test by using WE19 ....Put break point at include MSED7F03 at IF direction_in <> c_direct_incoming.
change the value of control_record_in-outmod to 1 or 3.
Note: Imp thing is............. there is a chase of missing segments which are requied in EDI Subsystem.
Thanks
Ramesh
Edited by: Ramesh on Mar 26, 2010 7:07 PM

EDI Outbound Purchase Order Please check

Hi,
My requirment is i have one outbound IDOC, i have to change some data inthe segment E1EDKA1 form some coustam tables
The Basic type is Orders05, i should do some changes in the segment E1EDKA1 based on E1EDKA1-PARVW in the exit EXIT_SAPLEINM_011,
i have written the code in the exit EXIT_SAPLEINM_011, Can any body pls check my code
TYPES:BEGIN OF ty_ztsd_ilnpurorg,
       bbbnr TYPE ztsd_ilnpurorg-bbbnr,
       bbsnr TYPE ztsd_ilnpurorg-bbsnr,
       bubkz TYPE ztsd_ilnpurorg-bubkz,
      END OF ty_ztsd_ilnpurorg,
      BEGIN OF ty_ztsd_ilnplant,
       bbbnr TYPE ztsd_ilnplant-bbbnr,
       bbsnr TYPE ztsd_ilnplant-bbsnr,
       bubkz TYPE ztsd_ilnplant-bubkz,
      END OF ty_ztsd_ilnplant,
      BEGIN OF ty_kna1,
       bbbnr TYPE kna1-bbbnr,
       bbsnr TYPE kna1-bbsnr,
       bubkz TYPE kna1-bubkz,
      END OF ty_kna1.
*&                    WORK AREA
DATA: lw_ztsd_ilnpurorg TYPE ty_ztsd_ilnpurorg,
      lw_ztsd_ilnplant TYPE ty_ztsd_ilnplant,
      lw_kna1           TYPE ty_kna1,
      lw_edidd          TYPE edidd,
      lw_e1edka1        TYPE e1edka1.
*&                    VARIABLES
DATA:l_bbbnr      TYPE ztsd_ilnpurorg-bbbnr,
     l_bbsnr      TYPE ztsd_ilnpurorg-bbsnr,
     l_bubkz      TYPE ztsd_ilnpurorg-bubkz,
     l_ilnnr      TYPE e1edka1-ilnnr,
     l_kna1_bbbnr TYPE kna1-bbbnr,
     l_kna1_bbsnr TYPE kna1-bbsnr,
     l_kna1_bubkz TYPE kna1-bubkz,
     l_kna1_partn TYPE e1edka1-partn,
     l_e1edka1_we TYPE e1edka1-ilnnr.
*&                    CONSTANTS
CONSTANTS:lc_orders05(8) TYPE c VALUE 'ORDERS05',
          lc_eledka1(7) TYPE c VALUE 'E1EDKA1'.
Clearing the workarea
CLEAR:lw_ztsd_ilnpurorg,
      lw_ztsd_ilnplant,
      lw_kna1,
      lw_edidd,
      lw_edidd_1,
      lw_e1edka1,
      lw_e1edp19.
*Checking for the Idoc type ORGERS05
IF control_record_out-idoctp = lc_orders05.
*Reading the EDIDD table for the segment E1EDKA1
READ TABLE dint_edidd INTO lw_edidd WITH KEY segnam = lc_eledka1.
IF sy-subrc = 0.
    MOVE lw_edidd-sdata TO lw_e1edka1.
ENDIF.
*checking the segment E1EDKA1-PARVW
CASE lw_e1edka1-parvw.
    WHEN 'AG'.
*Selecting the data required for conversion of E1EDKA1-ILNNR to Campina ILN number
      SELECT SINGLE bbbnr bbsnr bubkz
             INTO lw_ztsd_ilnpurorg
             FROM ztsd_ilnpurorg
             WHERE ekorg = lw_e1edka1-paorg.
      IF sy-subrc = 0.
        l_bbbnr = lw_ztsd_ilnpurorg-bbbnr.
        l_bbsnr = lw_ztsd_ilnpurorg-bbsnr.
        l_bubkz = lw_ztsd_ilnpurorg-bubkz.
      ENDIF.
      CONCATENATE l_bbbnr l_bbsnr l_bubkz INTO l_ilnnr.
*Conversion of E1EDKA1-ILNNR to Campina ILN number
      CLEAR dint_edidd.
      CLEAR lw_e1edka1.
      lw_e1edka1-ilnnr = l_ilnnr.
      MOVE lw_e1edka1 TO lw_edidd-sdata.
      MODIFY dint_edidd FROM lw_edidd TRANSPORTING sdata.
Clearing the workarea
CLEAR:lw_ztsd_ilnpurorg,
      lw_edidd,
      lw_e1edka1,
      l_bbbnr,
      l_bbsnr,
      l_bubkz,
      l_ilnnr.
    WHEN 'SP'.
*Selecting the data required for conversion of E1EDKA1-ILNNR to Plant ILN number
      SELECT SINGLE bbbnr bbsnr bubkz
             INTO lw_ztsd_ilnplant
             FROM ztsd_ilnplant
             WHERE werks = lw_e1edka1-lifnr.
      IF sy-subrc = 0.
        l_bbbnr = lw_ztsd_ilnplant-bbbnr.
        l_bbsnr = lw_ztsd_ilnplant-bbsnr.
        l_bubkz = lw_ztsd_ilnplant-bubkz.
      ENDIF.
      CONCATENATE l_bbbnr l_bbsnr l_bubkz INTO l_ilnnr.
*Conversion of E1EDKA1-ILNNR to Plant ILN number
      CLEAR dint_edidd.
      CLEAR lw_e1edka1.
      lw_e1edka1-ilnnr = l_ilnnr.
      MOVE lw_e1edka1 TO lw_edidd-sdata.
      MODIFY dint_edidd FROM lw_edidd. "TRANSPORTING sdata.
Clearing the workarea
CLEAR:lw_ztsd_ilnplant,
      lw_edidd,
      lw_e1edka1,
      l_bbbnr,
      l_bbsnr,
      l_bubkz,
      l_ilnnr.
    WHEN 'WE'.
*Selecting the data required for conversion of E1EDKA1-PARTN to ILN number from customer master KNA1
      SELECT SINGLE bbbnr bbsnr bubkz
             INTO lw_kna1
             FROM kna1
             WHERE kunnr = lw_e1edka1-partn.
      IF sy-subrc = 0.
        l_kna1_bbbnr = lw_kna1-bbbnr.
        l_kna1_bbsnr = lw_kna1-bbsnr.
        l_kna1_bubkz = lw_kna1-bubkz.
      ENDIF.
      CONCATENATE l_kna1_bbbnr l_kna1_bbsnr l_kna1_bubkz INTO l_kna1_partn.
      FREE:lw_ztsd_ilnplant.
*Selecting the data required for conversion of E1EDKA1-LIFNR to Plant ILN number
      SELECT SINGLE bbbnr bbsnr bubkz
             INTO lw_ztsd_ilnplant
             FROM ztsd_ilnplant
             WHERE werks = lw_e1edka1-lifnr.
      IF sy-subrc = 0.
        l_bbbnr = lw_ztsd_ilnplant-bbbnr.
        l_bbsnr = lw_ztsd_ilnplant-bbsnr.
        l_bubkz = lw_ztsd_ilnplant-bubkz.
      ENDIF.
      CONCATENATE l_bbbnr l_bbsnr l_bubkz INTO l_ilnnr.
*Checking PARTN and LIFNR for data
      IF l_kna1_partn IS NOT INITIAL.
        MOVE l_kna1_partn TO l_e1edka1_we.
      ELSE.
        MOVE l_ilnnr TO l_e1edka1_we.
      ENDIF.
*Conversion of E1EDKA1-PARTN to ILN number from customer master KNA1
             E1EDKA1-LIFNR to Plant ILN number
*Check and Convert PARTN and LIFNR and copy the field contents to ILNNR
      CLEAR dint_edidd.
      CLEAR lw_e1edka1.
      lw_e1edka1-partn = l_kna1_partn.
      lw_e1edka1-lifnr = l_ilnnr.
      lw_e1edka1-ilnnr = l_e1edka1_we.
      MOVE lw_e1edka1 TO lw_edidd-sdata.
      MODIFY dint_edidd FROM lw_edidd. "TRANSPORTING sdata.
*Free the work area and local variables
      FREE:lw_e1edka1,
           lw_edidd,
           l_bbbnr,
           l_bbsnr,
           l_bubkz,
           l_ilnnr.
ENDCASE.
It would be very help full if any body can quickely check the code and reply back,
Thanks in advance,
sai.

Dear
Please check setting in IMG SAP Supl.Rel.Management>SRM Server>Technical Basic Setting>Define Back end system for Product category.
Thanks & Regards
Rajendran

Error: Maintain EDI-outbound parameter for partner MSG09

Hi Gurus,
I have encountered an error message while I am trying to trigger an output in Purchase order, this should in turn create a Sales Order automatically in our process.
I knew that for this we need to maintain the partner profile in WE20.
But still I am facing the same problem as explained above.
Can any one tell me where exactly we assign the EDI Message type to the Purchase order output type in IMG. (Please specify the IMG PATH for this)
Can this setting will help in solving this problem ?
Please advise how to get rid of this.
Thanks in advance.
Regards,
Venkat

Go to WE20 - Vendor.
After you click the Vendor, you can see the Message type on the right.
Enter into the message type - Message Control.
You have to enter the Application (EF) , Message type (output type from the PO ) and the Process code.
The error code because of the missing data in the Message Control.

EDI Outbound IDOC Remove unused fields from segment

Hi All,
I am configuring a outbound idoc scenario for Message type ORDERS. The basic type for this message type is ORDERS05.
The segment E1EDKA1 has 44 fields, I need only the first field and the last field of this segment.
How do I remove the unused fields in this segment ? I Tried BD56 and BD32 But they are for removing the complete segment and so does not serve my purpose.
Any pointers to this issue is appreciable .
Regards,

Hi,
Segmetns of standard message types can be deleted from BD53. But I don't think deleting fields would be possible from segments of standard idoc type. What you can do is you can create your own custom idoc type with the fields you want and allign it with the standard message type ORDERS. This should solve your purpose.
BR,
Atanu Mukherjee

EDI Outbound sales order change

Hello,
I am triggering an EDI outbond sales order change.
I am useing ORDCHG and ORDERS05.
While setting up the Outband Partner profile,In the Message conterol tab
what is the Application,message function and process code.
Thanks in advance...

I am triggering an EDI outbond sales order change.
I am useing ORDCHG and ORDERS05.
While setting up the Outband Partner profile,In the Message conterol tab
what is the Application,message function and process code.
-The application is V1.
-You should enter in the Messagetype the Outputtype as used in NACE and the Sales Order Output creation. That can be BA00.
Make sure you make 2 entries in the partner profile: one where in the messagecontrol tab the change message Tab is ticked (in case the order changes) and one where it is not ticked (initial change).
-Message functionion can be used optionally, to differentiate to make it unique.
-The Processcode can be SD10 (or ME02 for PO change). You can use the dropdownbox if there is something configred yet.

EDI - Outbound Accounting Posting Journals to External System

Hi Experts,
I have a requirement in which I have to outbound
Accouting Journals to an external system...
Does standard SAP support such a functionality.
I looked at the outbound process code and was unable
to find anything on accounting. (which does make sense...) I also noticed that journal entry transactions such as FB01 do not have output controls like SD or MM.
Would I not be able to utilize standard idocs in this case?

Hi Rolmega,
Please refer the OSS note 616804 .That is exactly matching your requirement and guide you through out the development.
OSS note 616804.
Create a BAPI which can be used to create cash journal documents.
To do this, carry out the steps specified below in your system, or import the relevant Support Package.
1. In Transaction SE37, select the menu option 'Goto' -> 'Function Groups' -> 'Create group'. Create function group SAPLFCJ_BAPI with the short text 'BAPI for FI cash journal' and save it.
2. In Transaction SE37, create function module BAPI_CASHJOURNALDOC_CREATE in function group SAPLFCJ_BAPI in package CAJO with the short text 'Save FI cash journal documents' as a remote-enabled module.
a) Create the following function module documentation for the function module:
                        With BAPI BAPI_CASHJOURNALDOC_CREATE, you can save a document when you execute in the FI cash journal, in the same way as when you make an entry via the Interface Transaction FBCJ.
                        If the TESTRUN field is set, the system only carries out the checks and not the actual backup process when the database is updated.
                        If you want to save a cash journal document, the program that calls the BAPI has to execute the COMMIT WORK to update the document.
                        A document can contain several split rows.
                        You can post either expenses or receipts for each document. In other words, either the ITEMS-P_PAYMENTS or the ITEMS-P_RECEIPTS field has to be filled in all line items.
                        If the document contains several line items or entries in the control table, assigned net or tax base amounts are deleted.
                        The initiator has to assign the item number (ITEMS-POSITION_NUMBER) for all line items or for none.
                        If the initiator assigns one-time data, the item numbers (CPD_ITEMS-POSITION_NUMBER) have to correspond to the respective line item (ITEMS-POSITION_NUMBER). The same item number may be used in one one-time line item only.
                        If the extended withholding tax is active in the company code used, you can create only one line item and no split document for vendors or customers that are relevant for withholding tax.
                        The vendor has to be filled for all assigned rows of the withholding tax information (table WTAX_ITEMS).
                        If withholding tax information is to be assigned, the indicator for withholding tax type (WTAX_ITEMS-WTAXTYPE) has to be filled with a value that is defined in the vendor master record. In addition, the same indicator for the withholding tax type may be assigned in one line of the ITEMS table only. The system does not take into account the external item number for withholding tax information.
                        In the TAX_ITEMS table, the same tax code may be assigned in only one line.
                        If there are entries in the TAX_ITEMS table, every tax code or jurisdiction code of this table has to be assigned in at least one line of the ITEMS table or be able to be derived from the Customizing for the business transaction.
                        If, in Customizing, there are accounts and tax codes for interface transactions that are flagged as not ready for input, then the BAPI derives values that are transferred in the ITEMS table again and overwrites them if necessary.
                        A check recognizes that field HEADER-CHECK_NUMBER is filled when the BAPI is called.
                        You cannot use the BAPI to save a document in a cash journal if this cash journal is simultaneously blocked by another interface user or another BAPI initiator. When you execute the BAPI, the system also sets a block for other users.
                        The initiator of the BAPI can transfer additional field values via the EXTENSION_IN table and can process them further in a BADI called in the customer_function subroutine.
                        You cannot change saved documents or deposit checks.
a) Enter the following import parameters:
Parameter Name Type Associated Type Opt Pass Value Short text
HEADER          LIKE   BAPI_CJ_HEADER        X           Document header
Long text:
In the HEADER structure, you can assign the document header information of the cash journal document to be saved. Basically, the structure corresponds to the fields of the TCJ_DOCUMENTS table that are ready for input on the cash journal interface and which contain header information only.
TESTRUN         LIKE BAPI2021_HELP    X    X     Indicator for test run
                        TESTRUN                     without update
Long text:
If the TESTRUN field is set, the external structures transferred when the BAPI is called are assigned to the internal cash journal structures. The relevant checks are also carried out. However, no update occurs to save the document on the database.
b) Enter the following export parameters:
Parameter Name Type Associated Type Pass Value Short text
COMPANY_CODE    LIKE BAPI_CJ_HEADER   X          Company code
                        -COMP_CODE
Long text:
The COMPANY_CODE parameter contains the company code of the saved cash journal document.
CASH_JOURNAL_NUMBER LIKE BAPI_CJ_HEADER       Cash journal number
                          -CAJO_NUBMER
Long text:
The CASH_JOURNAL_NUMBER parameter contains the cash journal of the saved cash journal document.
FISCAL_YEAR         LIKE BAPI_CJ_KEY   X     Fiscal year
                          -FISC_YEAR
Long text:
The FISCAL_YEAR parameter contains the fiscal year of the saved cash journal document, but it is only filled for check totals documents.
CASH_JOURNAL_DOC_NO LIKE BAPI_CJ_KEY   X     Document number
                          -POSTING_NUMBER     cash journal document
Long text:
The CASH_JOURNAL_DOC_NO parameter contains the internal document number of the saved cash journal document.
c) Enter the following table parameters:
Parameter Name Type Associated Type Optional Short text
ITEMS           LIKE BAPI_CJ_ITEMS            Cash journal documentitems
Long text:
In the ITEMS table, you can assign the information for the line items of the cash journal document to be saved. Basically, the spaces in the table fields correspond to the fields of the TCJ_POSITIONS table that are ready for input on the cash journal interface and which contain item information only. You can assign several line items per document, in the same way as for the split lines that can be entered via the interface transaction.
TAX_ITMES     LIKE BAPI_CJ_TAX_ITEMS X      Cash journal tax items
Long text:
In the TAX_ITEMS table, you can assign tax information for the cash journal document to be saved. In this way, you can for example affect tax amounts derived from the system, in the same way as tax information is changed on the split window of the interface transaction.
CPD_ITEMS     LIKE BAPI_CJ_CPD_ITEMS X      One-time data
Long text:
In the CPD_ITEMS table, you can assign information for one-time customers or vendors that are contained in line items of the ITEMS table. Basically, the table fields correspond to the fields of the TCJ_CPD table, which are ready for input on the one-time window.
WTAX_ITEMS    LIKE BAPI_CJ_WTAX_ITEMS X      Withholding tax in the
                                                cash journal document
Long text:
In the WTAX_ITEMS table, you can assign information on the extended withholding tax for a vendor that is contained in a line item of the CJ_ITEMS table. Basically, the table fields correspond to the fields of the TCJ_WTAX_ITEMS table, which can be changed the withholding tax window.
EXTENSION_IN LIKE BAPIPAREX          X   Container for
                                             'Customer Exit'
Long text:
In the EXTENSION_IN parameter, you can transfer parameters that can be processed further in the BADI CJ_DOCUMENT, which the user of the BAPI BAPI_CASH_JOURNAL_CREATE has to implement.
For example, you can assign data to the TCJ_POSITIONS table in the form of Include CI_COBL or information profitability segments or real estate.
RETURN         LIKE BAPIRET2               Return parameter
Long text:
In Table RETURN, the messages of the program are returned to the initiator of the BAPI.
d) Save and activate the changes.
1. Using Transaction SE11, create data type (structure) BAPI_CJ_HEADER in Package CAJO with the short description 'Cash journal document header for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field            Data element
COMP_CODE        BUKRS
CAJO_NUMBER      CJNR
CURRENCY         WAERS
CURRENCY_ISO     WAERS_ISO
DOC_DATE         BLDAT
PSTNG_DATE       BUDAT
REF_DOC_NO       XBLNR1
BP_NAME          CJBPNAME
ALLOC_NMBR       DZUONR
TEXT1            CJDOCTEXT100
TEXT2            CJDOCTEXT30
CHECK_NUMBER     SCKNR_EB
CHECK_ISSUER     CJCHECKISSUER
BANK_KEY         BANKK
BANK_ACCT        BANKN
BANK_CTRY        BANKS
BANK_CTRY        BANKS
BANK_CTRY_ISO    BANKS_ISO
SCBANK_IND       LZBKZ
SUPCOUNTRY       LANDL
SUPCOUNTRY_ISO   LANDL_ISO
c) Save and activate the changes.
2. In Transaction SE11, create data type (structure) BAPI_CJ_ITEMS in Package CAJO with the short description 'Cash journal line item for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as enhancement category.
b) Create the following fields:
Field            Data element
POSITION_NUMBER CJBUZEI
TRANSACT_NUMBER CJTRANSNUMB
P_RECEIPTS       BAPIWRBTR
P_PAYMENTS       BAPIWRBTR
P_NET_AMOUNT     BAPIWRBTR
H_NET_PAYMENT_WT BAPIWRBTR
GL_ACCOUNT       HKONT
TAX_CODE         MWSKZ
TAXJURCODE       TXJCD
VENDOR_NO        LIFNR
CUSTOMER         KUNNR
POSITION_TEXT    CJPOSTEXT
BUS_AREA         GSBER
TR_PART_BA       PARGB
TRADE_ID         RASSC
CS_TRANS_T       RMVCT
FUNC_AREA        FKBER
CO_AREA          KOKRS
COSTCENTER       KOSTL
ACTTYPE          LSTAR
ORDERID          AUFNR
ORDER_ITNO       CO_POSNR
CALC_MOTIVE      BEMOT
COSTOBJECT       KSTRG
CO_BUSPROC       CO_PRZNR
PROFIT_CTR       PRCTR
PART_PRCTR       PPRCTR
WBS_ELEM         PS_POSID
NETWORK          NPLNR
ACTIVITY         VORNR
ASSETMAINO       BF_ANLN1
ASSETSUBNO       BF_ANLN2
VALUEDATE        BF_BZDAT
ASSETTRTYP       BF_ANBWA
PLANT            WERKS_D
VAL_TYPE         BWTAR_D
MATERIAL         MATNR
SALES_ORD        KDAUF
SCHED_LINE       KDEIN
S_ORD_ITEM       KDPOS
FM_AREA          FIKRS
FUNDS_CTR        FISTL
CMMT_ITEM        FIPOS
FUND             BP_GEBER
FUNDS_RES        KBLNR_FI
RES_ITEM         KBLPOS
PERSON_NO        PERNR_D
BUPLA            BUPLA
SECCO            SECCO
c) Save and activate the changes.
3. In Transaction SE11, create the data type (structure) BAPI_CJ_TAX_ITEMS in Package CAJO with the short description 'One-time data of cash journal line items for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field            Data element
TAX_CODE         MWSKZ
AMT_TAX          BAPITXBTR
AMT_BASE         BAPIFWBAS
TAXJURCODE       TXJCD
c) Save and activate the changes.
4. In Transaction SE11, create the data type (structure) BAPI_CJ_CPD_ITEMS in Package CAJO with the short description 'One-time data of cash journal line items for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category
b) Create the following fields:
Field            Data element
POSITION_NUMBER CJBUZEI
ANRED            ANRED
NAME             NAME1_GP
NAME_2           NAME2_GP
NAME_3           NAME3_GP
NAME_4           NAME4_GP
SOLE_PROP        STKZN
REP_NAME         REPRES
STREET           STRAS_GP
POSTL_CODE       PSTLZ
CITY             ORT01_GP
COUNTRY          LAND1_GP
COUNTRY_ISO      LAND1_ISO
PO_BOX           PFACH
POBX_PCD         PSTL2
REGION           REGIO
POBK_CURAC       PSKTO
BANK_ACCT        BANKN
BANK_NO          BANKL
BANK_CTRY        BANKS
BANK_CTRY_ISO    BANKS_ISO
CTRL_KEY         BKONT
BANK_REF         BKREF
INSTR_KEY        DTAWS
DME_IND          DTAMS
TAX_NO_1         STCD1
TAX_NO_2         STCD2
TAX_NO_3         STCD3
TAX_NO_4         STCD4
SLS_PUR_TX       STKZU
FITYP            J_1AFITP_D
TAX_NO_TY        J_1ATOID
EQUAL_TAX        STKZA
SPRAS            CHAR_LG_01
LANGU_ISO        LAISO
BUS_TYPE         GESTYP
IND_TYPE         INDTYP
c) Save and activate your changes.
5. In Transaction SE11, create the data type (structure) BAPI_CJ_WTAX_ITEMS in Package CAJO with the short description 'Withholding tax in cash journal document for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field            Data element
POSITION_NUMBER CJBUZEI
VENDOR_NO        LIFNR
WTAXTYPE         WITHT
WT_WITHCD        WT_WITHCD
W_TAX_BASE       BAPIQSSHB
WI_TAX_AMT       BAPIQBSHB
c) Save and activate the changes.
6. In Transaction SE11, create the data type (structure) BAPI_CJ_KEY in Package CAJO with the short description 'Key fields for cash journal documents'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field            Data element
FISC_YEAR        GJAHR
POSTING_NUMBER   CJBELNR
c) Save and activate the changes.
7. Using Transaction SE91, create the following messages for message class FCJ and select the 'Self-explanatory' field for each one:
a) 011: 'Document & & & was saved successfully.'
b) 012: 'Enter a gross amount.'
c) 013: 'Enter only the disbursement or incoming payment amount for each document.
d) 014: 'Enter the item numbers for all items or for none of them.'
e) 015: 'The number of tax items may not be larger than the number of items.'
f) 016: 'Only one tax item allowed per tax code/jurisdiction code.'
g) 017: 'Enter the item number for one-time items.'
h) 018: 'With several line items (split), do not enter any withholding tax items.'
i) 019: 'Business transaction without G/L account or tax code.'
j) 020: 'No line item with tax code/jurisdiction code of the tax item.'
k) 021: 'In company code & taxes without jurisdiction code.'
l) 022: 'Do not enter any tax item for posting indicator '3' (T007B-STBKZ)'
m) 023: 'Document could not be saved. Correct the errors listed'
n) 024: 'Business place + section code only with extended withholding tax.
o) 025: 'Net/tax base is deleted for several items or tax items'
p) 026: 'No line item corresponds to one-time item &.'
q) 027: 'Do not enter any withholding tax info if customer not w.tax-relevant'
r) 028: 'Do not enter any withholding tax info if vendor not w.tax-relevant'
s) 029: 'Do not enter any withholding tax info for G/L account posting.'
t) 030: 'Vendor in withholding tax information is not in line item.'
u) 031: 'Only one one-time item is allowed per item number.'
v) 032: 'Only one withholding tax item is allowed per withholding tax type.'
w) 033: 'Number of assigned withholding tax items deviates from master data.'
x) 034: 'No vendor required for business transaction.
y) 035: 'No customer required for business transaction.'
z) 036: 'Enter only receipts for checks.'
8. In Transaction SE37, call the FCJ_SAVE and FCJ_SAVE_DOCUMENT function modules in change mode.
a) Add import parameter I_XBAPI of TYPE BOOLEAN to these function modules. Select the Optional and Pass Value fields and enter the short text 'Indicator whether the call occurs from a BAPI'.
b) Also add the import parameters I_POSTING_NUMBER, LIKE, ISCJ_POSTINGS-POSTING_NUMBER for the function module FCJ_SAVE_DOCUMENT. Select the Optional and Pass Value fields.
c) Save and activate the changes.
9. In Transaction SE37, create the function module FCJ_SAVE_DOCUMENT_BALANCE_BAPI in the function group SAPLFCJ_PROCESS_MANAGER in Package CAJO with the short text 'Save cash journal document and balances for BAPI' as an update module with 'Start immed'.
a) Enter the following import parameters:
Parameter Name      Type Associated Type           Opt Pass Value
I_COMP_CODE         LIKE TCJ_C_JOURNALS-COMP_CODE       X
I_CAJO_NUMBER       LIKE TCJ_C_JOURNALS-CAJO_NUMBER     X
I_CURRENCY           LIKE TCJ_DOCUMENTS-CURRENCY         X
I_TYP               TYPE   CJTRANSTYP                     X
I_DISPLAY_PERIOD_LO LIKE SY-DATUM                        X
I_DISPLAY_PERIOD_HI LIKE SY-DATUM                        X
I_POSTING           LIKE    ISCJ_POSTINGS                  X
I_POSTING_NUMBER    LIKE ISCJ_POSTINGS-POSTING_NUMBER   X
b) Enter the following tables:
Parameter Name      Type Associated Type
ITCJ_POSTINGS       LIKE ISCJ_POSTINGS
ITCJ_WTAX_ITEMS     LIKE TCJ_WTAX_ITEMS
ITCJ_SPLIT_POSTINGS LIKE ISCJ_POSTINGS
ITCJ_CPD            LIKE TCJ_CPD
10. In Transaction SE18, define the BADI CJ_DOCUMENT. The corresponding interface is IF_EX_CJ_DOCUMENT.
               The method has the following 'Changing' parameter: Parameter             Type        Associated Type
C_ITCJ_SPLIT_POSTINGS Type        ISCJ_POSTINGS
C_ITCJ_SPLIT_TAXES    Type        ISCJ_POSTINGS
C_ITCJ_CPD              Type        TCJ_CPD
C_ITCJ_WTAX_ITEMS     Type        TCJ_WTAX_ITEMS
C_EXTENSION2           Type        BAPIPAREX
C_RETURN                Type        BAPIRET2
              You can use an implementation of this BADI to change the cash journal structures before the data check is processed.
1. Implement the attached corrections in your system.
2. In Transaction SE37, release the function module BAPI_CASHJORUNAL_DOC_CREATE via the menu path 'Function module' -> 'Release' -> 'Release'.
3. In Transaction SWO1, create the object type BUS2023.
a) Create the following key fields for the object type:
Key field           Name               Data type reference
CompanyCode       Company Code        TCJ_DOCUMENTS
                                        -COMP_CODE
CashJournalNumber Cash Journal Number TCJ_DOCUMENTS
                                        -CAJO_NUMBER
FiscalYear        Fiscal Year         TCJ_DOCUMENTS
                                        -FISC_YEAR
CashJournalDocNo Cash Journal        TCJ_DOCUMENTS
                  Document Number     -POSTING_NUMBER
b) Create the 'Create' method synchronously and instance-independent as an 'API function' with the name BAPI_CASHJOURNALDOC_CREATE.
                        Create the following parameters for the method: Parameter          Obj Type Imp. Man. Exp.
Header             BUS2023    X     X
Testrun            BUS2023    X
CompanyCode          BUS2023                X
CashJournalNumber   BUS2023                X
FiscalYear         BUS2023                X
CashJournalDocNo   BUS2023                X
Items               BUS2023    X     X
TaxItems           BUS2023    X
CPDItems           BUS2023    X
WTaxItems          BUS2023    X
ExtensionIn        BUS2023    X
Return             BUS2023                X
a) Create the 'ExistenceCheck' method synchronously and define the following source code:
                        begin_method existencecheck changing container.
                        DATA: l_mandt TYPE sy-mandt.
                        SELECT SINGLE mandt INTO l_mandt
                        FROM tcj_documents
                         WHERE comp_code = object-key-companycode
                           AND cajo_number = object-key-cashjournalnumber
                           AND fisc_year = space
                           AND posting_number = object-key-cashjournaldocno.
                        check sy-subrc <> 0.
                        exit_object_not_found.
                        end_method.
a) Under the menu option 'Goto' -> 'Documentation', define the following text for object type BUS2023:
                        A cash journal document is assigned to a cash journal and a company code.
                        It contains a unique document number from a company code-dependent number range interval that is independent of the number range interval of the G/L document. Cash journal documents are also numbered sequentially per company code and cash journal.
                        A cash journal document contains the offsetting entries for the G/L account of the cash journal in which G/L or person accounts are posted to for the business transaction.
                        You can save, delete, post or reverse a cash journal document. In the two last cases, there is a corresponding G/L document. This can be a receipt, a disbursement of cash, or the receipt of checks.
1. In Transaction BDBG, set up the IDOC processing for the object type BUS2023 and the method CREATE.
               The function module for ALE outbound processing with data refining is ALE_CASHJOURNALDOC_CREATE.
               The function module for ALE inbound processing is called IDOC_INPUT_CAJODOC_CREATE.
1. In Transaction 'SALE', maintain the ALE distribution. Here, maintain the steps generally required for a distribution process. Take into account the existing documentation of the operation. Execute the following steps for the BAPI used to save cash journal documents.
a) Maintain the distribution model under the path 'Model and Implement Business Processes' -> 'Maintain Distribution Model and Distribute Views'. The object name is 'CashJournalDoc' and the method name is 'Create'.
b) Execute the menu option 'Edit' -> 'Model view' -> 'Distribute' for the selected model view.
c) Select the path 'Model and Implement Business Processes' -> 'Partner Profiles and Time of Processing' -> 'Generate Partner Profiles'. (See corresponding documentation in document OALE_AUTOPARTN_BD82.) Enter the selected model view in the distribution model and the selected target system as the partner system.
2. To monitor the distribution of the IDOCs, use Transaction BD87 in both the sender system and the receiver system, and you can reach it via the path 'Tools' -> 'ALE' -> 'ALE Administration' -> 'Monitor' -> 'Status Monitor'. The relevant message type is CASHJOURNALDOC_CREATE.

EDI outbound

Similar Messages

Maybe you are looking for