Initial upload of Stock in WM without creation Transfer order

Hi All,
I want perform intial stock upload (movement type 561) in a Plant and Storage Location. The Storage location is WM activated.
So I need to post 561 movement in IM i need then manual move the stock from Interium Bin to normal bin through Tcode: LT01.
Is it possible that I can upload the stock both in Stroage location and respective bin in one step without creating Transfer order.

Please check these answered links:
WM(Stock Upload WM)
Urgent-uploading initial stock in wm
Initial load for WM after MM implementation
Edited by: Afshad Irani on May 7, 2010 5:35 PM

Similar Messages

Initial Uploading of Stock to MM

Hi Experts,
I need to upload the initial stock as MM stock. When I tried with MType 561, it goes to WM (Warehouse Management) Stock. So, I do not want to upload the stock to WM. I need to upload to MM Stock. Your valuable inputs are solicited.
K Bharathi

Shiva Ram wrote:
When you upload the stock, don't enter the storage location details (only maintain plant).
if you load stock, then you have to have a storage location, except it is special stock like stock at a subcontractor, or stock in a customer consignment.
Shiva Ram wrote:
Or use the storage location that is NOT tied to a warehouse.
> Regards,
I agree to this statement.
However, if you have to load stock and your location is setup to be warehouse managed, then you should test the real case. What can you gain from a test load to MM only when you finally have to load to a warehouse managed location?
if you load with 561 into a warehouse managed location, then the stock goes to storage type 998. And from there you do a WM internal movement (create a TO) to move the material from 998 storage type to the final bins.
No need for an extra MM movement, this adds just complexity without any benefit.
Depending on the complexity of the warehouse you might be able to post it to the final bins directly with the MM movement, you just need a small customizing for the movement 561.
In any case the WM-TO to move from 998 storage type to final bin can be created as well with a load program

Sales order stock on delivery document and transfer order

Hi all,
At my current client I have a requirement where we need to put stock against sales order (sales order stock E). So, being a MTO process we create production order and perform goods reciept to unrestricted stock. To avoid getting picked up by a different sales order, we move the stock to sales order stock using 412 E (tcode: MB1B). Here are the issues I am facing currently:
1. Is there a direct way of receiving production order directly to sales order stock?
2. I couldn't find a way to do the first, so I am currently receiving production order against unrestricted inventory and then move it using MB1B. So, the stock can be seen to assigned to sales order.
2a. When I create delivery it is not consuming same stock, it is consuming inventory out of unrestricted stock (if any, in case no inventory is available it throws error of 0 available quantity). Once I have assigned sales order stock why is it still looking into unrestricted? Is it due to the requirement type which is assigned. Do I need to change the item category so availability will check sales order stock (similar to item category TAB)?
2b. This probably will be resolved if I get the delivery fixed but we have SAP WM and during TO creation I don't see the special stock reference filled in? I tested this process with item category ZTAB (copy of TAB) which creates purchase requisition and it seems to be working but I don't need the purchase req for my case.
3. This is more of an accounting issue: when I attempt to move stock from unrestricted to sales order stock using 412 E, I was getting "Account XXXXX is not assigned to cost center". So, I went in an assigned a cost center to this cost element. IS THIS REQUIRED & WHAT IS THE RELEVANCE as it takes stock out of inventory.
I understand it crosses other functional areas but even if you can clarify 1 part of it, will be very helpful.
Thanks.
Naren

Dear Friend
You are telling that it is MTO scenario and you are posting stocks into unrestricted stocks
This is entirely wrong
This is happening because of a simple thing missing in your sales order item category configuration in VOV7 that is special stock indicator E is missing which should be there
This is the cause of whole problem
MTO item categories will have special stock indicator E in standards
In MTO based on the sales order production order is triggered and stocks are receipted against sales order and not into unrestricted use by defaut in standard
You will receive MTO stocks as sales order stocks in your plant only in standard
But it is not happening for you because of stock indicator E in VOV7 of your sales order item category is missing
Posting MTO stock in to unrestricted use is meaningless and the same is happening because of a slight miss out in setting in VOV7
This is the solution for issue no 1
For issue no 2
You have created the sales order( MTO order) without special stock indicator E and now you are doing a transfer posting in MB1B with 412 E referencing the order no sales order stocks that is Fine
You are getting an error that only zero qty is available either at delivery or at pgi eventhough in MMBE you will find sales order stocks in your order name
This is happening because
Reservation in MB1B is done with special stock indicator E for sales order
But the same sales order is not created with special stock indicator E in VA01 during creation
There is a mismatch
Hence the system is not able to sense while the order comes for delivery there are already stocks are reserved
By inputting special stock indicator E for sales order item category the whole issues will get solved
By doing that there is no need to do MB1B itself
The first step itself will get corrected as the stocks will be posted to sales order stocks no need for MB1B
No need to touch TAB make it ZTAB as it is meant for a different purpose it is for individual purchase order not to be used for MTO
*By marking the special stock indicator as E in your sales order item category your entire issue will be resolved*
Issue no 3
MTO is based on costing for which you have take the help of FI person
Note Very important
If U make the settings now in item category it will not work for the existing or already created order
With existing orders it will have the same error as the order is created without special stock indicator E
Only for new orders it will work and from Now on it will work
Test it with new order cycle starting from VA01
Please let me know this issue has got solved or not?
I am 200 % sure it will get solved
Regards
Raja

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.

Initial Uploading of Stock in Transit

Hi all
We are going Live by next week. But there are some materials which has been already dispatched and the stock are in Transit. But the Material will reach the Receiving plant after Go-Live only.
How to accomodate the Stock in Transit when doing Initial upalod.
Kindly suggest.
Regards
Madhesh Kumar

Hi,
Alternative is to re-enter purchase orders but treat them as a normal external vendor process rather than inter-company. To do this you would need to create the external vendors (exactly same as inter-company ones) but the STO config will be based on inter-company vendor number.
This way you don't need to worry about creating outbound deliveries etc.
Thanks.

Error when CRETING STOCK INITIAL UPLOAD USING MB1C

THE ERROR IS : The number range for document number assaignment has not been maintained in the year 2011 for the transaction event type WA.
we are getting this error while creating stock initial upload using t.code MB1C.
and another ERROR is : Number range for trans/event type WA in year 2011 does not exist.
please give me the solution to this error.
Moderator message:
Locked. Reason: 1) basic question 2) improper use of capitals
Please read forum rules before posting.
Edited by: Csaba Szommer on Jan 7, 2012 8:18 AM

Hi Dear,
Use T . Code u2013 OMBT, then go to change interval , then go to edit > insert year (f6) and mention in year 9999 and choose the number range interval from number to number and mention in current number is 0 and save exit.
Hope it helps you.
Regards,
Yawar Khan

Initial entry of stock (561) using MB1C

Hi all
Can someone help me understand how to create initial entry of stock using references.
I see there are options to create "To purchase order", "To Reservation", etc. Do they mean that we can create initial entry with reference to purchase order?
Also there is option to create with reference to Material document. What kind of Material documents can be used as reference?
Thanks in advance
Regards
Mui

Hi,
All this options are for other goods receipts means without reference to purchase order.
otions are To Reservation, To Order.This order means not Purchase order i.e Production Order or Internal Order.
Initial entry are used to Upload the stock at initial stage i.e at the time of Cutover strategy,we uploading the initial stock which is present at plant at SAP system and after that only we process the normal transaction like PO, MIGO..
Regards
Sanjay L

Intial upload of Stock in Transit Material with in plant / Inter company

Hi Friends,
How can we do Intial upload of Stock in Transit Material with in plant / Inter company.
In this case accounting entries has already completed while doing post goods issue (thru SD route) or in 1st step 301 mov. type.
Now the material is in transit. While we go to new system how can do this without hit of aacounting entries.
I tried 565, it Intial upload of stock to Blocked, so accounting entries took place.
Regards
Sai Krishna

Hi,
What I am proposing is:
At this juncture both plants accounting has been done in legacy.
Coming to new system whatever stock we upload that much value only updated in receiving plant. In reality there is difference between legacy & new system in this case. In legacy stock in transit value also added in receiving plant (since we did PGI). If we do stock upload with 565 mov. type .. intial entry to blocked stock i.e value of inventory is matching the legacy.
Actual receiveal of material do transfer posting from blocked stock to unresticted stock.
What is your opinion.
We won't upload the G/L inventory, it will come thru stock upload for kishore infor.
Regards
Sai Krishna

Initial entry of stock balance

hi everbody
what will be the account posting in case
1) of initial entry of stock balance
2) of gr witout reference to po (mvt type 501)
in both case raw material account is hitting with transaction key bsx posting key 89 then what will be secind accounting entry ahd with what posting key.and which account will be hit(nature of a/c).
points will be given

Hi,
The following are accounts are updated with the transaction keys
1.Initial entry of stock balances:
Material stock account debited with account key BSX with posting key 89.
Intial entry account is credited with account key GBB-BSA posting key-91 and the account is expence account type.
2.GR without PO.
Material stock account debited with account key BSX with posting key 89.
Other purchases(purchases made without PO) account credited with accounting key GBB-ZOB with posting key 91and the account is of expence nature.
Thanks,
Rambhupal reddy

What is use of Item Category N(non-stock item) in BOM creation

Dear Experts,
What is use of Item Category N(non-stock item) in BOM creation ?
regards
rajakarthik

Hi,
This item category is used for components which are not kept in stock if they are used in a bill of material (BOM). Non-stock items can be entered in the BOM with or without a master record. To enter a non-stock item without a master record, you must simply enter a descriptive text.
When you use this item category, the system automatically creates a purchase requisition for these components,
Special functions
The following functions are supported for non-stock items
You maintain purchasing data for non-stock items in the bill of material.
In the planning run, the system generates purchase requisitions
instead of dependent requirements for components that are procured directly. When you configure your R/3 System for MRP, you can define whether direct procurement is triggered by the planning run or by production order management.
Product costing processes take valuation data from the BOM item.
The system determines the release strategy on the basis of the price data you enter. The material group is required to produce a purchase requisition.
Pavan

Upload QI stock in SAP system

We are in cut over face of implementation project.
We have already QI stock for multiple materials outside SAP system, now we want to upload this stock in SAP system.
What is the best approach in this situation?

SAP has a standard process for this.
In the QM plant settings on the tab insp. lot creation, you shoudl find a field call "InstypeForInspStock".
Per the SAP standard, you enter 0800. (you can try another inspection type, but this one works!)
Make sure in config you have defined a task list usage for inspection type 0800.
Make sure you have not turned on QM for any of the materials you are planning on loading inventory for. If you already did, you'll have to use QA08 to deactivate all inspection types before doing the inventory load.
Load all your inventory, including the QI stock into QI stock via IM.
Use QA08 to turn on all your inspection types. On the QA08 screen you'll find an indictor "Activate despite insp. stock". Make sure this is clicked on when running QA08.
One you have run QA08 for all the materials, all those with stock in QI should now have inspection lots associated with them.
They will be an 08 origin and 0800 inspection typ.
Be careful. Once the inspection types are created, you won't be able to load additional qtys to QI via IM. You only get one shot.
FF

Probleme with Initial custmer consignment stock

Dear All,
Initially when client went to SAP. He had some consignment stock at customer site, in SAP same stock maintained as consignment stock, Eventually some of the consignment stock return back, In sap client done normal return delivery to get back these stock without any reference, so now he came to know that it result in double inventory. Also result in increase in stock account balance is standing in clearing acct. now he want to adjust this double inventory stock ,
So pls tell me how he can adjust initial customer consignment stock, also how adjust the account entries.
Pls Help

Hi,
Whenever we get back the stock from customer consignment.we should use consignment pick up doc.type KA and subsequent delivery.this transaction will add the customer consignment stock to the main stock
So in your case you done normal return process so consignment stock is same and extra qty stock is added to main stock.thats why inventory is doubled.
So reverse this normal return process and again do consignment process.
Thank you,

Asset Initial Upload & reporting for uploaded value

Hi SAP Gurus,
I have uploaded the asset data using AS91 and also updated the GL values in OASV.
The initial upload seems to be all correct in this manner since TB is tallying.
However when i view the FA reports for the date of upload i am finding discrepancies in the Accumulated Depreciation values as shown in the report & the values uplaoded in AS91.
Let me explain further, say for eg. the Cost of the asset was Rs. 10,000/- and Accumulated Depreciation as per legacy (as on date of upload) is Rs. 1858/-. However the actual Accumulated Depreciation should have been Rs. 1863 --- the diffference in legacy data was due to runding offs in previous months.
Now when i uploaded the intial data i used the legacy figures i.e. Rs. 10,000 & Rs. 1858 since trial balance had to be tallied.
However when i run reports in FA for the initial upload date, i find that the reports are showing the Acc. Depn (plan values) as Rs. 1863 & not the value that i have uploaded.
What possibly is the reason for this ?
Can anyone tell me any report to view only the uploaded information ?
Points will be awarded for useful answers.
Thanks & Regards
Piyush Kothari

Hi,
There is an error appearing as below:
"Report date 31.08.2007 is invalid for this report.
Reports of this kind can only be run for the last day of the period in which the last depreciation posting run took place (or in a subsequent period) in the relevant fiscal year.
It is not possible to run a report on posted depreciation in a fiscal year in which no depreciation posting run has yet taken place."
My legacy upload date was 31.08.2007.
When i run for 31.12.2007 (last period in the fiscal year for which dep. run has taken place) then the results are ok.
But still i would like to assign some points to you since this would have helped indeed.
Thanks
Piyush Kothari

Check amount of transition stock during inbound delivery creation

I want to move stock between plans, therefore I have the following steps:
1. Stock Transfer Order (STO), e.g. 500 pieces
2. Sending plant: MIGO (GI for STO) with MT 351 to post to transition stock, e.g. 100 pieces
3. Receiving plant: Inbound Delivery with reference to STO VL31N
4. process Inbound delivery in warehouse (SAP-WM)
The question is:
During step 3, when accessing VL31N the system proposes the full order quantity (e.g. 500 pc.)
I can change the amount to any amount I like, e.g 240 pieces.
How can I tell SAP, that Inbound delivery creation is only possible for the amount
which has been posted to stock in transition (100 pieces)
I want an error/warning message in case user wants to create Inbound delivery quantity higher than the amount that has been posted to transition stock.
Any ideas?

MIGO in sending Plant?
How it is possible? MIGO means, Goods receipt. This should be in Receiving plant.
Sending plant should do the PGI
MIRO in receiving plant
Billing in sending plant
Payment from Receiving palnt and clearing in sending plant
Correct me if i am wrong
Thanks

Initial upload of Stock in WM without creation Transfer order

Similar Messages

Maybe you are looking for