Inbound and out bound

hi all
can anybody give ,when we do inbound and outbound delivery
regards
bhavani

Hi
<b>Inbound delivery</b>
The significant advantage of depicting the goods receipt process through the inbound delivery function is that the company can execute many processes in advance, even before the actual goods receipt posting takes place. In this case, all the necessary information is available beforehand as notification of the inbound delivery will be released ahead of time by the supplier.
The inbound delivery describes exactly which materials or pallets can be received on what date and at what time.
The following functions are available with the goods receipt process for inbound deliveries:
Material availabiltiy status for MRP run
Batch information
The batch split that is already possible for outbound deliveries is also available for inbound deliveries, since batches are often first identified in the inbound delivery.
Inventory management of packaging materials
Goods receipt for inbound deliveries
Determination of goods receiving point
<b>Outbound delivery:</b>
Outbound delivery is similar to Inbound delivery.Before Goods issue to Customer against Sales order, Out bound delivery ill be created contains all the information like shipping-planning information , Quantity etc.Based on this document, picking and packing will be done.after all the required processes completed, then Post goods issue will be done.
Outbound delivery supports all shipping activities including picking, packing, transportation and goods issue. During the outbound delivery process, shipping-planning information is recorded, status of shipping activities is monitored and data accumulated during shipping processing is documented. When the outbound delivery is created, the shipping activities, such as picking or delivery scheduling, are initiated, and data that is generated during shipping processing is included in the delivery.
Process:
Inbound Delivery:
PO -> Inbound delivery -> GR
Outbound delivery
Sales order-> Outbound delivery - > goods issue
Regards
Ramakrishna

Similar Messages

Inbound and out bound problem at we 20

hi
in bw system at we20 tcode
i have out bound is
RSRQST
inbound is
RSINFO
REEEND
in ecc system
outbound is
RSINFO
REEEND
inbound is
RSRQST
is the sequence is correct or not?
ple let me know

OUTBOUND parameters:
- RSINFO: Enter the port that you found or created in step a).
The package size is 1. Select the option "Pass IDocs
immediately" as output mode. The basis Idoc type is RSINFO.
- RSSEND: Enter the port which you found or created in step a).
The package size is 1. Select the option "Pass IDocs
immediately" as output mode.
INBOUND parameter.
Enter message type RSRQST
The process code of the message type is RSRQ. Select the option "start immediately".
Thanks
Reddy

Telesales Inbound and Out bound

Hi,
Can any one please help me out with the configuration documentation related to Inbound and Outbound Telesales which needs to done before creating Interaction Center WinClient Profiles along with configuration related CTI.
Regards
Vinod

OUTBOUND parameters:
- RSINFO: Enter the port that you found or created in step a).
The package size is 1. Select the option "Pass IDocs
immediately" as output mode. The basis Idoc type is RSINFO.
- RSSEND: Enter the port which you found or created in step a).
The package size is 1. Select the option "Pass IDocs
immediately" as output mode.
INBOUND parameter.
Enter message type RSRQST
The process code of the message type is RSRQ. Select the option "start immediately".
Thanks
Reddy

For inbound and out bound interface

what is inbound interface and outbound interface.what is diff b/w inbound and outbound interface.
thnx

Hi,
The interface through which data comes inside SAP is inbound interface on the other hand the interface through which data goes out of SAP is called outbound interface.
Rgds
Mayank

What is meant by in bound and out bound delivery

hai sap sd gurus,
please tell me, wht is meant by in bound and out bound delivery?

>
peruru sreenivas wrote:
> hai sap sd gurus,
> please tell me, wht is meant by in bound and out bound delivery?
Hi Sreeni,
See any delivery that is inbound i.e. bound to come in like Returns from Customer or Delivery from a Vendor to us or any other delivery which is coming to us.....
Similarly any delivery that is outbound i.e. bound to go out like the deliveries we do to customers are Outbound deliveries
Reward if helpful
Regards
Abhishek

In Bound and Out Bound Queues

Hello All,
Can some body explain what is meant by a Queue.
Why do we require queues to transfer the the data
In our land Scape we have XI through XI messages(Pay load) are transfered
My question is Now a days many of the customers implementing XI
So do we require Queue registration
If Yes please explain me breifly.
Thanks &Regards,
Praveen Kondabal.

Hi Praveen,
XI messages for inbound processing are placed in inbound queues of Integration Engine and placing them in outbound queues carries out outbound processing. As a part of Integration Engine configuration, we register XI queues. By registering queues used by the Integration Engine, we intimate qRFC the technical names of these queues
Do refer these ~
/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
/people/vasanthakumar.balasubramani2/blog/2005/12/21/complete-reference-for-idoc-queuing-and-monitoring
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
Regards,
Madhu

Incoming purchase order vs out bound goods receipt processing

Hi
any body know how to develop an interface for below requrement
creating an interface for incoming purchase order creation and out bound goods receipt processing
please let me know anybody knows this
Thanks in advance,
Best regards
Alleiah

I done Purchase order inbound ...
you have to set up partner profile at we20 like message type,idoc type,port..
Message type : orders
idoc type : orders05,once you done it creates the purchase order,for testing you can use we19 ,enter data manually and you can see the status at we02 or we05 transaction
Reward Points if it is helpful
Thanks
Seshu

In-Bound & Out-bound interfaces list of GL, AP & PO modules

Hi,
GoodDay, I'm working with GL, AP & PO modules. Please let me know both In-bound and Out-bound interfaces list of those three modules.
Regards,
Ram.

For 11i, these are listed at http://irep.oracle.com
HTH
Srini Chavali

SUBTITLES CUT OFF AND OUT OF BOUNDING TEXT BOX

SUBTITLES CUT OFF AND OUT OF BOUNDING TEXT BOX
by Ben Martin on Jun 24, 2008 at 9:57:39 am
I use Encore version 2.0 and have problem with subtitles on a 30 minutes video. I have not imported these subtitles, but made them, one clip at the time. The first 10 minutes is fine, each subtitle is within a bounding box (the bounding box was stretched up to the first inner rectangle of the Safe Area). They can be seen fine on the timeline and on the DVD.
However from one particular subtitle onwards, all the subtitles clips seem to suffer from the same problem. When I play them on the timeline the long subtitles are cut off at the right end. When I click on them within the monitor, I see that they are not within a normal bounding box. Instead the text is sort of "embedded" within a structure of white squares (similar to a bounding box), but any attempt to strecth that "structure" by pulling a square with a text tool, only deform and extend the text itself.
I have tried to create a blank subtitle clip after the last "good" one, using the Add subtitle button on the monitor, but it won't create an empty bounding box within which I could type or paste the text. It works if I try to create an empty clip in the "good" area of the time line (the first 10 minutes), but not before or after that first bad clip I mentioned above. It is as if there was something bad on the timeline and any attempt to create a proper bounding box clip is impossible.
Is there a setting that I can change? or is it a bug in the programme?
Any help would be appreciated. Thanks.
Ben Martin
Payday

In order to aviod stretching the existing text, you must use text tool to resize the boundry box.

Sales Order no and IDOC No Link table for Sales Out bound IDOC ORDRSP

Hi Friends
How to find Sales Order no and IDOC No Link table for Sales Out bound IDOC ORDRSP.
Thanks in Advance.
SR

Hi
If the idoc is managed by message, the link are stored in GOS (Obeject Service)
U can try to use the function module NREL_GET_NEIGHBOURHOOD
If you put
IS_OBJECT-OBJKEY = <sales document>
IS_OBJECT-OBJTYPE = <business object> (I think BUS2032)
the function returns the idoc
or if you put
IS_OBJECT-OBJKEY = <idoc number>
IS_OBJECT-OBJTYPE = <business object> (I think IDOC)
the function returns the sales order
You can investigate that function module in order to find out the tables
Max

In OUT Bound of a Jaxws provider, how can we stop the provider invoking its endpoint and send a response back?

Hi One & All
While we are working on Delegate(provider) for JAXWS client handler in Weblogic10 , we have some technical issues and need some assistance.
Problem Description
In OUTBound of a provider, how can we stop the provider invoking its endpoint and send a response back?
Example:
I have a provider with some handlers configured for both IN and OUT flows. When the Jaxws provider is making a request, the OUTBound Handler gets invoked and in this Handler I would like to stop invoking actual endpoint and send back my own response. That means I should be able to tell the Handler chain to stop further processing of this flow, set a response message into message exchange and invoke the IN flow. How do I do that?
This kind of mediation/interception is possible in standard specifications like JAX-WS, Servlets etc… wondering if Weblogic10 JAXWS provides any sort of this kind.
Also we would like to know who is invoking a provider endpo int in JAXWS stack in weblogic10? Is it an OUTBound handler at the end of handler chain or some other transport component after the handler chain?
Thanks in Advance
Suresh
Edited by: user12494412 on Jan 22, 2010 7:06 AM

I completely agree with this....I have used Windows and Skype for many years. I recently installed an older version of Skype to run on Windows 8.1 because the new version is SO AWFUL. As much as I prefer the older version (6.14), the daily number of SPAM CONTACT requests is rediculous and most are just variations of the same spammer. Maybe it is time to look for a replacement for both?

Multiple inbound and outbound plugs

Hi Experts,
Can anybody give an example scenario where we compulsorily need multiple inbound and outbound plugs for a view??

Hi snakar rao ,
Suppose we have three views, a , b, c. Suppose we have a requirement like we need a button move_to_b on a, a button back in b which will move back to a, a button move_to_c on b and a button move_to_initial screen on c.
in this case
we need one out bound plug in a which will be connected to inbound of b
one out bound plug in b which will be connected to inbound of c.
in this case a needs two inbound plugs, one is for navigating from b and the other is for navigating from c
if there is a requirement like we need to navigate from a to c directly also, in this case c need one more inbound plug thats to connect the inbound plug from a.
Regards
Sarath

Out bound delivery against STO

Hi
My client requirement is to trace every movement against STO i-e system should track each GR against each GI against STO.
Meaning when we issue a goods against STO system should track against which GI user post GR as in the system there is no standard available to track this activity.
We will see a possibility that the we have posted a outbound delivery against STO and the GOODS ISSUE and similarly do the inbound delivery and then GR against STO this is the only way to track the Goods Receipts against Good Issue.
It is only suggestions kindly correct me if I am wrong and one more help how the system create out bound delivery against STO.
Regards,
Tahir

HI,
Whatever you mention is correct

Out bound idoc creation urgent!!!!!!!!!!!!

Hi experts,
          I am given a task to create an out bound IDOC which would be input to TIBCO, which must be triggered every time Good issue transaction is completed by either VT02N or VL02N transaction up pressing SAVE.
          IDOC is to have fields from Customize tables apart from standard SAP tables, so was asked to create an own IDOC ( eg: Z--Idoc).
         Please tell me how to create the idoc, and also the method to trigger it and how to populate the IDOC ( program etc).
          Use full inputs would be promtly rewarded.
Regards,
Ram.

Sample code in the below:
REPORT zhefrn_idoc_extract_fi LINE-SIZE 160.
Purpose
This program extracts FI postings and create IDOCs
Description
An IDOC of type ACC_GL_POSTING01 is created from the extracted
FI-data.
*- Extract data from BKPF and BSEG
*- Build the IDOC control record. Use structure EDIDC.
*- Build and internal table of structure EDIDD with IDOC segments.
EDIDD contains some keyfields, but the data segment field is simply
one string, as EDIDD is used for all type of IDOCs. To simplify the
process of building this string, use the SAP datastructures with the
same name as the segment. E.g for segment E1BPACHE08 use structure
E1BPACHE08.
*- Use function module MASTER_IDOC_DISTRIBUTE to create the IDOCs.
Remember to commit.
Important: This program can not handle multiple documents, so all
postings must have the same key (Company code, currency code,
postingdate, document date) so that they can be posted in the same
document. *If the program should handle multiple documents, data
should be split *according to the key, and an IDOC created for each
document.
Standard types
TABLES:
bkpf, "Accounting Document header
bseg. "Accounting Document Segment
TEDS1. "IDoc status values
Standard types
TYPES:
BEGIN OF st_bkpf,
    bukrs LIKE bkpf-bukrs,
    belnr LIKE bkpf-belnr,
    gjahr LIKE bkpf-gjahr,
    blart LIKE bkpf-blart,
    bldat LIKE bkpf-bldat,
    budat LIKE bkpf-budat,
    monat LIKE bkpf-monat,
    waers LIKE bkpf-waers,
END OF st_bkpf,
BEGIN OF st_extract,
    bukrs LIKE bkpf-bukrs,
    belnr LIKE bkpf-belnr,
    gjahr LIKE bkpf-gjahr,
    blart LIKE bkpf-blart,
    bldat LIKE bkpf-bldat,
    budat LIKE bkpf-budat,
    monat LIKE bkpf-monat,
    waers LIKE bkpf-waers,
    hkont LIKE bseg-hkont,
    bschl LIKE bseg-bschl,
    shkzg LIKE bseg-shkzg, "Debit/credit indicator
    dmbtr LIKE bseg-dmbtr,
    wrbtr LIKE bseg-wrbtr,
    dmbe2 LIKE bseg-dmbe2,
END OF st_extract.
Table types
TYPES: tt_bkpf     TYPE STANDARD TABLE OF st_bkpf,
       tt_extract TYPE STANDARD TABLE OF st_extract,
       tt_edidd    TYPE STANDARD TABLE OF edidd,
       tt_edidc    TYPE STANDARD TABLE OF edidc.
Internal tables
DATA:
G/L Doc header
gi_bkpf     TYPE tt_bkpf,
G/L extracted data
gi_extract TYPE tt_extract,
IDOC segment data
gi_edidd    TYPE tt_edidd,
Return table
gi_communication_idoc_control TYPE tt_edidc.
Global variables
DATA:
WA for internal tables
g_bkpf      TYPE st_bkpf,
g_extract   TYPE st_extract,
g_edidd     LIKE edidd,
*-- IDOC structures:
IDOC control record
g_idoc_control_record LIKE edidc,
G/L document header
g_e1bpache08 LIKE e1bpache08,
G/L Account Line Items
g_e1bpacgl08 LIKE e1bpacgl08,
Line Item Currency Fields
g_e1bpaccr08 LIKE e1bpaccr08,
Return table from MASTER_IDOC_DISTRIBUTE
g_communication_idoc_control LIKE edidc.
Selection screen
SELECTION-SCREEN BEGIN OF BLOCK 1 WITH FRAME.
SELECT-OPTIONS: a_bukrs FOR bkpf-bukrs,
                a_budat FOR bkpf-budat,
                a_hkont FOR bseg-hkont,
                a_usnam FOR bkpf-usnam DEFAULT 'WMHEFRN'.
PARAMETERS:     p_create AS CHECKBOX.
SELECTION-SCREEN END OF BLOCK 1.
SELECTION-SCREEN BEGIN OF BLOCK 2 WITH FRAME.
IDOC control record - Receiver
PARAMETERS:
p_rcvpor LIKE edidc-rcvpor DEFAULT 'PORT-HFN', "Rec. Port
p_rcvprn LIKE edidc-rcvprn DEFAULT 'WMHEFRN', "Rec. Partn. number
p_rcvprt LIKE edidc-rcvprt DEFAULT 'US',       "Rec. Partn. type.
p_rcvpfc LIKE edidc-sndpfc DEFAULT '§§'.       "Partner function
SELECTION-SCREEN END OF BLOCK 2.
SELECTION-SCREEN BEGIN OF BLOCK 3 WITH FRAME.
IDOC control record - Sender
PARAMETERS:
p_sndpor LIKE edidc-sndpor DEFAULT 'SAPC46', "Send. Port
p_sndprn LIKE edidc-sndprn DEFAULT 'WMHEFRN', "Send. Partn.number
p_sndprt LIKE edidc-sndprt DEFAULT 'US'.       "Send. Partn. type.
p_sndpfc LIKE edidc-sndpfc DEFAULT '§P'.       "Send. Partn. funct.
SELECTION-SCREEN END OF BLOCK 3.
Start of selection
START-OF-SELECTION.
PERFORM initialize.
PERFORM extract_data.
PERFORM build_idoc_control_record.
PERFORM build_idoc_segments.
IF p_create = 'X'.
    PERFORM create_idocs.
ENDIF.
PERFORM write_report.
*&      Form INITIALIZE
FORM initialize.
REFRESH: gi_bkpf,
           gi_extract,
           gi_edidd.
CLEAR: g_idoc_control_record.
ENDFORM.                    " INITIALIZE
*&      Form EXTRACT_DATA
Extract FI postings to internal table gi_extract
FORM extract_data.
Read BKPF
SELECT bukrs
          belnr
          gjahr
          blart
          bldat
          budat
          monat
          waers
    FROM bkpf
    APPENDING CORRESPONDING FIELDS OF TABLE gi_bkpf
    WHERE bukrs IN a_bukrs AND
          budat IN a_budat AND
          usnam IN a_usnam.
LOOP AT gi_bkpf INTO g_bkpf.
    SELECT hkont
           bschl
           shkzg
           dmbtr
           wrbtr
           dmbe2
      FROM bseg
      INTO CORRESPONDING FIELDS OF g_extract
      WHERE bukrs = g_bkpf-bukrs AND
            belnr = g_bkpf-belnr AND
            gjahr = g_bkpf-gjahr.
      MOVE-CORRESPONDING g_bkpf TO g_extract.
      APPEND g_extract TO gi_extract.
      CLEAR g_extract.
    ENDSELECT.
ENDLOOP.
SORT gi_extract BY belnr.
ENDFORM.                    " EXTRACT_DATA
*&      Form WRITE_REPORT
Writes a report showing the selected data, and generated IDOCs
and errors
FORM write_report.
WRITE: / 'Extracted data' COLOR COL_GROUP INTENSIFIED ON.
LOOP AT gi_extract INTO g_extract.
    AT NEW belnr.
      SKIP 1.
      FORMAT COLOR COL_GROUP INTENSIFIED ON.
      WRITE: 'Document', g_extract-belnr.
      FORMAT RESET.
      NEW-LINE.
    ENDAT.
    WRITE: /
      g_extract-bukrs,
      g_extract-belnr,
      g_extract-gjahr,
      g_extract-blart,
      g_extract-bldat,
      g_extract-budat,
      g_extract-monat,
      g_extract-waers,
      g_extract-hkont,
      g_extract-bschl,
      g_extract-shkzg,
      g_extract-dmbtr,
      g_extract-wrbtr,
      g_extract-dmbe2.
ENDLOOP.
Write generated IDOCS
ULINE.
SKIP 2.
WRITE: / 'Generated IDOCs' COLOR COL_GROUP INTENSIFIED ON.
WRITE: / g_idoc_control_record.
LOOP AT gi_edidd INTO g_edidd.
    WRITE: / g_edidd-segnam(10) COLOR COL_KEY, g_edidd-sdata(140).
ENDLOOP.
Write staus codes returned from function module MASTER_IDOC_DISTRIBUTE
IF p_create = 'X'.
    ULINE.
    SKIP 2.
    WRITE: / 'Returncoides from function module MASTER_IDOC_DISTRIBUTE'
              COLOR COL_GROUP INTENSIFIED ON.
    LOOP AT gi_communication_idoc_control INTO
            g_communication_idoc_control.
Find error message
select single
from TEDS1
      WRITE: / g_communication_idoc_control-docnum,
               g_communication_idoc_control-status.
    ENDLOOP.
ENDIF.
ENDFORM.                    " WRITE_REPORT
*&      Form BUILD_IDOC_CONTROL_RECORD
The IDOC control record contains message type, port and
partnerinformation
FORM build_idoc_control_record.
g_idoc_control_record-mestyp = 'ACC_GL_POSTING'.   "Message type
g_idoc_control_record-idoctp = 'ACC_GL_POSTING01'. "IDOC type
Receiver
g_idoc_control_record-rcvpor = p_rcvpor. "Port
g_idoc_control_record-rcvprn = p_rcvprn. "Partner number
g_idoc_control_record-rcvprt = p_rcvprt. "Partner type
g_idoc_control_record-rcvpfc = p_rcvpfc. "Partner function
Sender
g_idoc_control_record-sndpor = p_sndpor. "Port
g_idoc_control_record-sndprn = p_sndprn. "Partner number
g_idoc_control_record-sndprt = p_sndprt. "Partner type
g_idoc_control_record-sndpfc = p_sndpfc. "Partner function
ENDFORM.                    " BUILD_IDOC_CONTROL_RECORD
*&      Form BUILD_IDOC_SEGMENTS
      text
--> p1        text
<-- p2        text
FORM build_idoc_segments.
DATA: l_transdate(8) TYPE c,
        l_itemnr TYPE i.
CLEAR l_itemnr.
LOOP AT gi_extract INTO g_extract.
Build data - The structures from the underlying BAPI are used to
simplify thje work of building the data part of the IDOC
*-- Document header segment E1BPACHE08
*-- The document header should only be generated in the first loop
    CLEAR g_edidd.
    IF sy-tabix = 1.
      CLEAR g_e1bpache08.
      g_edidd-segnam = 'E1BPACHE08'.
      g_edidd-segnum = 1.
      g_e1bpache08-obj_type   = 'BKPFI'.
      g_e1bpache08-obj_key    = '127387347'.
      g_e1bpache08-obj_sys    = 'APOCLNT800'.
      g_e1bpache08-username   = 'WMHEFRN'.
      g_e1bpache08-header_txt = 'Humle er godt'.
      g_e1bpache08-comp_code = g_extract-bukrs.
      g_e1bpache08-fisc_year = g_extract-gjahr.
      g_e1bpache08-doc_date   = g_extract-budat.
      g_e1bpache08-pstng_date = g_extract-bldat.
      g_e1bpache08-trans_date = sy-datum.
      g_e1bpache08-fis_period = g_extract-monat.
      g_e1bpache08-doc_type   = 'SA'.
      MOVE g_e1bpache08 TO g_edidd-sdata.
      APPEND g_edidd TO gi_edidd.
    ENDIF.
*-- Line item segment E1BPACGL08
    CLEAR g_e1bpacgl08.
    CLEAR g_edidd.
    l_itemnr = l_itemnr + 1.
    g_edidd-segnam               = 'E1BPACGL08'.
    g_edidd-segnum = 2.
    g_e1bpacgl08-itemno_acc      = l_itemnr.
    g_e1bpacgl08-gl_account      = g_extract-hkont.
    g_e1bpacgl08-pstng_date      = g_extract-bldat.
    g_e1bpacgl08-item_text       = 'Halli Hallo'.
    MOVE g_e1bpacgl08 TO g_edidd-sdata.
    APPEND g_edidd TO gi_edidd.
*-- Line Item Currency Fields segment E1BPACCR08
    CLEAR g_e1bpaccr08.
    CLEAR g_edidd.
    g_edidd-segnam          = 'E1BPACCR08'.
    g_edidd-segnum = 3.
    g_e1bpaccr08-itemno_acc = l_itemnr.
    g_e1bpaccr08-curr_type = '00'.
    g_e1bpaccr08-currency   = g_extract-waers.
    IF g_extract-shkzg = 'H'.
      g_extract-dmbtr = g_extract-dmbtr * -1.
    ENDIF.
    CALL FUNCTION 'CURRENCY_AMOUNT_IDOC_TO_SAP'
         EXPORTING
              currency    = g_extract-waers
              idoc_amount = g_extract-dmbtr
         IMPORTING
              sap_amount = g_e1bpaccr08-amt_doccur.
    MOVE g_e1bpaccr08 TO g_edidd-sdata.
    APPEND g_edidd TO gi_edidd.
ENDLOOP.
SORT gi_edidd BY segnum.
LOOP AT gi_edidd INTO g_edidd.
    g_edidd-segnum = sy-tabix.
    MODIFY gi_edidd FROM g_edidd.
ENDLOOP.
SORT gi_edidd BY segnum.
ENDFORM.                    " BUILD_IDOC_SEGMENTS
*&      Form CREATE_IDOCS
Create IDOCS
FORM create_idocs.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
       EXPORTING
            master_idoc_control            = g_idoc_control_record
       TABLES
         communication_idoc_control     = gi_communication_idoc_control
            master_idoc_data               = gi_edidd
      EXCEPTIONS
           error_in_idoc_control          = 1
           error_writing_idoc_status      = 2
           error_in_idoc_data             = 3
           sending_logical_system_unknown = 4
           OTHERS                         = 5
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
Remember to commit !
    COMMIT WORK.
ENDIF.
ENDFORM.                    " CREATE_IDOCS
Process outbound IDOCs
Process the outbound IDOCs using program RSEOUT00. The program can be executed from SE38. The IDOC should now have status code 03 Data passed to port OK.
Create inbound IDOCs
The inbound IDOC can be created from the outbound IDOC using transaction WE12 Modification of Outbound file Triggering inbound Procg. The name of the target file is not important, but it must not have the same name as the source file.
Note that the program returns an error, but an inpund IDOC is created.
Source and Sender
The source file must have the same name and path as the outbound file in the partner profile. In this example it is created in the TMP directory which seem to exist in the root directory.
Recipient
Process inbound IDOCs
The inbound IDOC should now have staus code 64. Use program RBDAPP01 to process the inbound IDOC.
Please give me reward points If it is useful.
Thanks
Murali Poli

Out bound IDOC creation

Hi experts,
I am given a task to create an out bound IDOC which would be input to TIBCO, which must be triggered every time Good issue transaction is completed by either VT02N or VL02N transaction up pressing SAVE.
IDOC is to have fields from Customize tables apart from standard SAP tables, so was asked to create an own IDOC ( eg: Z--Idoc).
Please tell me how to create the idoc, and also the method to trigger it and how to populate the IDOC ( program etc).
Use full inputs would be promtly rewarded.
Regards,
Ram.

Hi
Creation of Custom IDOc type and message Type
First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
take the Basis help to create them.
1.First create segments in WE31 Tcode with the required dataelements
2.Create the Basic Idoc Type in WE30
release the Segments and IDOC type.
3.Create Message type in We81
4.Assign the message type to IDOC type in WE82 T code
5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for Inbound) Outbound Fun module
7.Create Workflow setting if needed ..
8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
9.Define setting for fun module in BD51
10.In BD51 Define the settings for Fun module..
10.Assign the Processs Code to Fun mod`ule
Outbound Interface
PROCESS DIAGRAM for Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
? The name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
? The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
c_SEGMENT_type1.
The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
The ALE Layer handles the sending of the IDOC to the receiving system.
Error Handling (see Step 7b).
Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
Declare a structure of type MCMAILOBJ for sending instructions.
Enter values for the internal table based on structure MCMAILOBJ
For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
Enter your message type and execute.
Status should be green, double click on one of the Idocs you have created to view its contents.
If a problem has occurred click on Status which will give you a description of the error.
Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
Click on each individual segment and view the content to check that the correct data has been read.
If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
Regards
Anji

Inbound and out bound

Similar Messages

Maybe you are looking for