Transfer Order number in MSEG table

Hi,
I am a Technical team member and while preparing Technical Specification for a Report I came accross a problem that when we do a PGI the Transfer Order field in the table MSEG does not get updated.
My requirement is to get the Transfer Order number from the Material document, and I don't understand why this field isn't getting updated in MSEG table with reference Transfer order when one does a PGI.
Please let me know if there is any configuration I need to check with so that I can go with this info to my Functional team.
Appreciate your help in this regard.
Thanks and Regards,
Saleem.

Hi Saleem
In MSEG you can find TR number (MSEG-TBNUM). Take MBLNR from MSEG and pass into LTAK table. There you can find TO Number (LTAK-TANUM)
Hope it helps
regards
Srinivas
reward if it is useful

Similar Messages

Transfer order number

Hi...
Can anyone tell me field name for Proposed Transfer Order Number in PP module.
Regards,
Sandy

Hi Saleem
In MSEG you can find TR number (MSEG-TBNUM). Take MBLNR from MSEG and pass into LTAK table. There you can find TO Number (LTAK-TANUM)
Hope it helps
regards
Srinivas
reward if it is useful

Transfer Order number for Production order

Hi,
what is the best way to get the transfer order number (LTAK-TANUM) for picking for a production order?
Picking can occur first in IM (via MB1A for example) or in WM (via LP10). Requirement Tracking Number cannot be used as it has only a length of 10 characters (production order number up to 12 characters).
Reservation number (LTAK-RSNUM) is only filled in case picking is done from IM first.
Cheers
Mathias

Hi,
how are other companies handling this if they want to pick from the warehouse (e.g. using CO27) for a production order and the production order number has 12 characters? The bin (LTAP-VLPLA) and the requirement number (LTAK-BENUM) only have up to 10 characters.
Is there a standard way in SAP to print out the complete 12 character number on the picking list? I could not find another field where the production order number appears.
P.S. There are already some production order types in use that have a number range with 12 characters.
Cheers
Mathias

Want to fetch data from AFVU table with input of order number from AUFK table

Hi,
I have a requrement in report where in the user wil enter the order number from AUFK table and it should display detais like job code condition code (from AFVU table) along with other fields. There is no relation ship between AFVU and AUFK. Can anybody help me in getting the replation ship between 2 tables. What is the table that iam missing and where can i find that relationship and fetch records for that order number?

Check if this helps..
AUFK -> AFKO -> AFVU
AUFK-AUFNR = AFKO-AUFNR
AFKO-AUFPL = AFVU-AUFPL
Hope this helps.

Updation of PO number in MSEG table

Hai All,
When I make a transfer posting of material to sub-contractor (541 mvmt type) using transaction MB1B, against a Sub-contracting PO, the PO number is not getting updated in the MSEG table. I need this for creation of a form. Also the PO history is also not getting updated.
Kindly advice me.
Regards
sampath

Hi,
The basic concept of subcontracting is that the supply of materials to the vendor is not directly linked to a specific subcontract PO and so the link is not established between the two.
Effectively you are asking your subcontractor to provide you with a service and you are providing them with some components, but the process somehow assumes that they just keep a lage stock of your components and you replenish them from time to time with stock transfers (goods issues or deliveries).
I guess that the best you can do is to manually enter the PO number in the header text of the 541 movement (assuming that you are doing these manually and not via ME2o).
Steve B

To save the sales order number in custom table while creation of the order.

Hi Experts,
Does there exist any exit to save the sales order number in a custom table while the sales order is created in VA01. The requirement is to capture the sales order number in a Z table when a field (payment terms ) is changed during the sales order creation.
Regards,
Sunitha

Hi Sunita,
You can store your data in the User exit MV45AFZZ in the form 'userexit_save_document'.
You can navigate to MV45AFZZ from SE38 wherein an access key needs to be generated for that program, if you know to implement enhancement points then you can create an implicit enhancement point in this form without generating an access Key.
Regards,
Ravi Kiran

No Order number in QMEL table for Q3 notification type

Hi All,
I am new to QM part, and trying to understand concepts here.
a notifcation got created for a internal problem encountered in Production process. Notifcation type Q3, Order number, Operation Number and othere required data was maintained.
But when I look into QMEL table AUFNR field is blank. Is this a standard behaviour ?
Actually this information is required in Custom report-->The link between Notifcation number and Order number. Is there a different way of fetcheing this information.
**please note that no inspection lot is created here.
Regards,
Avinash

Hello Avinash,
In QMEL; AUFNR is Maintenance Order number, Usually used in PM notifications.
You can use QMEL- FERTAUFNR : Prod. Order field to get link between Notification and Order.
(CO_AUFNR = QM Order.)
Amol.

Required a user Exit After Transfer Order Number is genarated?

hi
guys
I need a userexit when ever the Transfer order is generated i need to call the form .can any one help me on these
Thanks in advance
Moderator Message: First help yourself by doing some R&D. If you do not stop asking such lazy questions, then we will have to delete your User ID.
Edited by: kishan P on Dec 8, 2010 11:14 PM

Hi,
Check the enhancement PPCO0007:Exit when saving production order.
Exit is EXIT_SAPLCOZV_001
Thanks,
Ramakrishna

Order number in bseg table

Where this field (BSEG-AUFNR) gets populated from ?
Some threads says it is an internal order. What does it mean ?
Thanks
Rita

Hi,
This filed is used for order. It is a field for FI for recording data in col order. Eg if you are going for customer down payment orer field will be there if you want to record it in internal order in co. like you will find this field in fi entries based on your field status setting for the respective accounts.
Regards

Capture Production order number during 541 in MB1B

Dear All,
I want to capture production order number field during 541 (reference to purchase order) in mb1b, so i could get production order number in MSEG table.
Process flow.
1. External processing with PP02 control key
2. SubCon Purchase order with Automatic Account assignment of Production order
3. MB1B with 541 Movement type reference to SuBcon Purchase order (In this i want to capture production order field automatically).
Br,
Swapnil

swapnil vaidya wrote:
Dear All,
>
> I want to capture production order number field during 541 (reference to purchase order) in mb1b, so i could get production order number in MSEG table.
>
> Process flow.
> 1. External processing with PP02 control key
> 2. SubCon Purchase order with Automatic Account assignment of Production order
> 3. MB1B with 541 Movement type reference to SuBcon Purchase order (In this i want to capture production order field automatically).
>
> Br,
>
> Swapnil
Hi,
You can get this Goto MB1B-provide 541-Select Environment in menu bar-oder-This will ask you to provide the reference document which is the production order.
Thanks

Read Routing and work center details from transfer order

Hello
I am using transaction LT31 to print a form for the transfer order.
The customer wants me to print a field that is in the work center details of the routing for this material and plant.
I can see this data with transaction CA02 where i enter material and plant,and then the work centers are beeing displayed.From here i can double click on the work center and see the field Supply area that i have to print.
My answer now is,how to read details on the work center starting from my transfer order number.Which is the table connection between transfer order table LTAK and the tables where i can find the work center details.
Thank you

I have found the solution:
ltak-tanum = mseg-tbnum
read aufnr from mseg and go to afko
mseg-aufnr = afko-aufnr
read plnnr from afko and go to plpo
afko-plnnr = plpo-plnnr
from plpo read arbid and go to crhd
plpo-arbid = crhd-objid
from here,we can find the arbpl and the field that i was looking for PRVBE

Automatic form generation on creation transfer order for delivery note?

Hi,
I have to create a form that should automatically be generated on the creation of a transfer order for delivery note. How do I trigger this automatic creation of the form? And how can the transfer order number be passed to my print program?
Thx!

hi christophe,
To issue the delivery output, go to transaction VL02N.
Then go to EXTRAS-> OUTPUT->HEADER->EDIT
In the Message output screen enter the relevant output type created for the delivery.
Choose the relevant medium of output.
Choose Simple Mail, in this case the field NAST-NACHA will be having a value of 7.
Specify the Partner Function; in this case it is MA -> Mail partner address
Select the Communication Method for the output type maintained.
This will take you to the SAPOFFICE screen.
Enter there the E-Mail Address to which you want to send the delivery document as PDF.
A mail will be sent to the e-mail address of the E-Mail Address specified, with the delivery output form as a PDF attachment.
hope it will help u ..
*& Report ZZ_TEST                                                     *
REPORT zz_test                                 .
INCLUDE zz_test_top.
INCLUDE zz_test01.
      FORM entry                                                    *
--> RETURN_CODE                                                   *
--> US_SCREEN                                                     *
FORM entry USING return_code us_screen.
CLEAR retcode.
xscreen = us_screen.
PERFORM processing USING us_screen.
CASE retcode.
    WHEN 0.
      return_code = 0.
    WHEN 3.
      return_code = 3.
    WHEN OTHERS.
      return_code = 1.
ENDCASE.
ENDFORM.                    "entry
*& Include           ZZ_TEST_TOP                                      *
TABLES : nast,
           tnapr.
TYPES : BEGIN OF t_SOUDNAMEI1.
        INCLUDE STRUCTURE SOUDNAMEI1.
TYPES : END OF t_SOUDNAMEI1.
Internal Table declarations
DATA: i_otf TYPE itcoo OCCURS 0 WITH HEADER LINE,
i_tline TYPE TABLE OF tline WITH HEADER LINE,
i_receivers TYPE TABLE OF somlreci1 WITH HEADER LINE,
i_record LIKE solisti1 OCCURS 0 WITH HEADER LINE,
*Objects to send mail.
i_objpack LIKE sopcklsti1 OCCURS 0 WITH HEADER LINE,
i_objtxt LIKE solisti1 OCCURS 0 WITH HEADER LINE,
i_objbin LIKE solisti1 OCCURS 0 WITH HEADER LINE,
i_reclist LIKE somlreci1 OCCURS 0 WITH HEADER LINE,
i_lips LIKE lips OCCURS 0 WITH HEADER LINE,
i_SOUDNAMEI1 TYPE STANDARD TABLE OF t_SOUDNAMEI1.
Work Area declarations
DATA:w_objhead TYPE soli_tab,
wa_control_parameters TYPE ssfctrlop,
wa_output_options TYPE ssfcompop,
w_return TYPE ssfcrescl,
w_doc_chng TYPE sodocchgi1,
w_data TYPE sodocchgi1,
w_buffer TYPE string,"To convert from 132 to 255
wa_SOUDNAMEI1 TYPE t_SOUDNAMEI1,
Variables declarations
w_form_name TYPE rs38l_fnam,
w_len_in LIKE sood-objlen,
w_len_out LIKE sood-objlen,
w_len_outn TYPE i,
w_lines_txt TYPE i,
w_lines_bin TYPE i,
retcode      TYPE sy-subrc,
xscreen      TYPE c,
w_spld TYPE usr01-spld,
w_receiver TYPE SOXNA-FULLNAME,
w_OBJ_RECORD TYPE OBJ_RECORD,
w_user type sy-uname,
w_email TYPE ad_smtpadr.
Constants Declaration
CONSTANTS : c_x TYPE c VALUE 'X',
              c_atrate(1) TYPE c VALUE '@'.
*& Include           ZZ_TEST01                                        *
      FORM PROCESSING                                               *
FORM processing USING proc_screen.
SELECT * FROM lips
    INTO TABLE i_lips
    WHERE vbeln = nast-objky.
Call Function module to Getfunction Module name Generated by Smartform
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      formname           = tnapr-sform
    IMPORTING
      fm_name            = w_form_name
    EXCEPTIONS
      no_form            = 1
      no_function_module = 2
      OTHERS             = 3.
IF sy-subrc <> 0.
    retcode = sy-subrc.
ENDIF.
CLEAR : wa_control_parameters,
          wa_output_options.
CASE nast-nacha.
    WHEN '1'.
      wa_control_parameters-device    = 'PRINTER'.
    WHEN '7'.
      DATA: l_email TYPE ad_smtpadr.
      wa_output_options-tdnoprev = c_x.
      wa_control_parameters-getotf = c_x.
To get the default output device maintained in the
User profile
     SELECT SINGLE spld FROM usr01
      INTO w_spld
      WHERE bname EQ nast-usnam.
      IF sy-subrc EQ 0.
        MOVE w_spld TO wa_output_options-tddest   .
      ENDIF.
      wa_output_options-tdnoprev = c_x.
      wa_control_parameters-getotf = c_x.
To get the email address maintained for the particular output
      CALL FUNCTION 'NAST_GET_MESSAGE_OBJECT_RECV'
        EXPORTING
          pi_objkey             = nast-tdname
        IMPORTING
          pe_addr               = w_receiver
        CHANGING
          pc_objhandle          = w_obj_record
        EXCEPTIONS
          maildata_not_readable = 1
          OTHERS                = 2.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
       WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      IF w_receiver NA c_atrate.
To retrieve the E-Mail Id in case we get the User name from NAST
        CLEAR wa_soudnamei1.
        REFRESH i_soudnamei1.
        MOVE w_receiver TO wa_soudnamei1-fullname.
To get the user name
        CALL FUNCTION 'SO_NAME_CONVERT_API1'
          EXPORTING
            name            = wa_soudnamei1
          TABLES
            names           = i_soudnamei1
          EXCEPTIONS
            user_not_exist = 1
            parameter_error = 2
            x_error         = 3
            OTHERS          = 4.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        CLEAR wa_soudnamei1.
        READ TABLE i_soudnamei1 INTO wa_soudnamei1 INDEX 1.
        MOVE wa_soudnamei1-sapname TO w_user.
To get the e-mail Id maintained in the user profile
        CALL FUNCTION 'FTR_CORR_CHECK_EMAIL_SAP_USER'
          EXPORTING
            i_user              = w_user
          IMPORTING
            e_email_address     = l_email
          EXCEPTIONS
            mail_address        = 1
            determination_error = 2
            OTHERS              = 3.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        MOVE l_email TO w_receiver.
      ENDIF.
      MOVE w_receiver TO w_email.
ENDCASE.
wa_control_parameters-no_dialog = c_x.
wa_control_parameters-langu     = nast-spras .
wa_output_options-tdteleland    = nast-tland.
wa_output_options-tdtelenum     = nast-telfx .
wa_output_options-tdsenddate    = nast-erdat .
wa_output_options-tdsendtime    = nast-eruhr .
wa_output_options-tddataset     = nast-dsnam .
wa_output_options-tdsuffix1     = nast-dsuf1 .
wa_output_options-tdsuffix2     = nast-dsuf2 .
wa_output_options-tdimmed       = nast-dimme .
wa_output_options-tddelete      = nast-delet .
wa_output_options-tdautority    = nast-tdautority.
wa_output_options-tdcovtitle    = nast-tdcovtitle .
wa_output_options-tdcover       = nast-tdocover .
wa_output_options-tdreceiver    = nast-tdreceiver.
wa_output_options-tddivision    = nast-tddivision.
wa_output_options-tdcopies      = nast-anzal .
wa_output_options-tdnewid       = c_x.
wa_output_options-tdarmod       = nast-tdarmod.
wa_output_options-tdnoarmch     = c_x.
CALL FUNCTION w_form_name
    EXPORTING
     archive_index      = toa_dara
     archive_parameters = arc_params
      control_parameters = wa_control_parameters
      output_options     = wa_output_options
      user_settings      = ' '
    IMPORTING
      job_output_info    = w_return
    TABLES
      it_lips            = i_lips
    EXCEPTIONS
      formatting_error   = 1
      internal_error     = 2
      send_error         = 3
      user_canceled      = 4
      OTHERS             = 5.
IF nast-nacha EQ 7 AND sy-subrc EQ 0.
    i_otf[] = w_return-otfdata[].
    CALL FUNCTION 'CONVERT_OTF'
      EXPORTING
        format                = 'PDF'
        max_linewidth         = 132
      IMPORTING
        bin_filesize          = w_len_in
      TABLES
        otf                   = i_otf
        lines                 = i_tline
      EXCEPTIONS
        err_max_linewidth     = 1
        err_format            = 2
        err_conv_not_possible = 3
        OTHERS                = 4.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
Convert PDF from 132 to 255.
    LOOP AT i_tline.
Replacing space by ~
      TRANSLATE i_tline USING ' ~'.
      CONCATENATE w_buffer i_tline INTO w_buffer.
    ENDLOOP.
Replacing ~ by space
    TRANSLATE w_buffer USING '~ '.
    DO.
      i_record = w_buffer.
Appending 255 characters as a record
      APPEND i_record.
      SHIFT w_buffer LEFT BY 255 PLACES.
      IF w_buffer IS INITIAL.
        EXIT.
      ENDIF.
    ENDDO.
    REFRESH: i_reclist,
    i_objtxt,
    i_objbin,
    i_objpack.
    CLEAR w_objhead.
Object with PDF.
    i_objbin[] = i_record[].
    DESCRIBE TABLE i_objbin LINES w_lines_bin.
Document information.
    w_doc_chng-obj_name = 'Smartform'.
    w_doc_chng-expiry_dat = sy-datum + 10.
    CONCATENATE 'Delivery' 'Note'
    INTO w_doc_chng-obj_descr.
*w_doc_chng-obj_descr = 'Smart form output'.
    w_doc_chng-sensitivty = 'F'. "Functional object
    w_doc_chng-doc_size = w_lines_txt * 255.
Pack to main body as RAW.
Obj. to be transported not in binary form
    CLEAR i_objpack-transf_bin.
Start line of object header in transport packet
    i_objpack-head_start = 1.
Number of lines of an object header in object packet
    i_objpack-head_num = 0.
Start line of object contents in an object packet
    i_objpack-body_start = 1.
Number of lines of the object contents in an object packet
    i_objpack-body_num = w_lines_txt.
Code for document class
    i_objpack-doc_type = 'RAW'.
    APPEND i_objpack.
Packing as PDF.
    i_objpack-transf_bin = 'X'.
    i_objpack-head_start = 1.
    i_objpack-head_num = 1.
    i_objpack-body_start = 1.
    i_objpack-body_num = w_lines_bin.
    i_objpack-doc_type = 'PDF'.
    i_objpack-obj_name = 'Smartform'.
    CONCATENATE 'Delivery' 'Note' '.pdf'
    INTO i_objpack-obj_descr.
    i_objpack-doc_size = w_lines_bin * 255.
    APPEND i_objpack.
Document information.
    CLEAR i_reclist.
e-mail receivers.
    i_reclist-receiver = w_email.
    i_reclist-express = 'X'.
    i_reclist-rec_type = 'U'. "Internet address
    APPEND i_reclist.
sending mail.
    CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
      EXPORTING
        document_data              = w_doc_chng
        put_in_outbox              = 'X'
      TABLES
        packing_list               = i_objpack
        object_header              = w_objhead
        contents_bin               = i_objbin
   contents_txt               = i_objtxt
        receivers                  = i_reclist
      EXCEPTIONS
        too_many_receivers         = 1
        document_not_sent          = 2
        document_type_not_exist    = 3
        operation_no_authorization = 4
        parameter_error            = 5
        x_error                    = 6
        enqueue_error              = 7
        OTHERS                     = 8.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
ENDIF.
ENDFORM.                    "processing

IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq

Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03     Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PM

IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.

Project name field in WM Transfer order

Hi Guys
I need to print Transfer order print out
Which Table and field I need to take
Project number (Original format) DSA01.000045.00002

Hi,
Can you give me by which transaction code you are taking print of Transfer Order.
I think regarding this you must take a help of yr abper's.
Sandeep

Logic for finding transfer order creation date for a given delivery??

Hi,
I am trying to find a logic for connecting the table LTAK which has ERDAT as the T.O. creation date with LIKP/ LIPS table.
Can you please help me with this information.
Regards,
Peeyoosh.

Hi,
Go to LTAP to get the transfer order number based on delivery ltap-vbeln. Then got to ltak to get the Creation date.
Hope it helps
Vinod.

Transfer Order number in MSEG table

Similar Messages

Maybe you are looking for