Regarding plant creation

hai,
when we create a plant as copy as option thyen it stores in the entries
suppose whenever we create the plant by using new entries option it has not stored in the table entries
what is main differance between these two options?
regards
ramu.

Hello Ramu
There is a big deiffernce between creating plant using copy function and without it.
Normally when you go for a new implementation u use new entry function as no plant exists that time in the system. so you have to make so many entries, then connect that plant to other entities of SAP-MM like Pur org, std pur org ,co code etc.
but in a running system if u need to create a plant then u mostly use copy as function because then only basic information u have to provide and other things system will pick from the existing plant only. so table entries required b\manually reduces to a very minimum extent.
i hope this helps, if still any query please tell us.
regards
Yogesh

Similar Messages

Plant Creation Date

Hi Experts,
How can we know the plant creation date of one of our plant created nearly 6-8 months back.
Regards
GR

Hello
Try table DBTABLOG with:
tabname = 'T001W'
logkey = concatenate client and plant (like '333ABC' - 333 - client and ABC - plant)
optype = 'I' (insert)
You will have DBTABLOG-LOGDATE (date of creation) and DBTABLOG-LOGTIME (time of creation)

Table for Plant Creation Date

Hi,
Can anyone tel me the table name for Plant Creation date .?
I searched in SDN but DBLOGTAB in my case has ZERO entries .Is thr any other way ?

Hello,
So i hope you get the reason why your are not getting the table changes in DBTABLOG
You should take help of the basis team for doing this. PLease go through the SAP documentation for details:
[http://help.sap.com/saphelp_nw04/helpdata/en/7e/c81ec852c511d182c50000e829fbfe/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/7e/c81ec852c511d182c50000e829fbfe/content.htm]
[http://help.sap.com/saphelp_nw2004s/helpdata/EN/32/a479f0e083fc4386e66380e932497e/content.htm|http://help.sap.com/saphelp_nw2004s/helpdata/EN/32/a479f0e083fc4386e66380e932497e/content.htm]
BR,
Suhas

Problem regarding the creation of Table using CSS.

Hi ,
Here I have a Problem regarding the creation of Table using CSS.
In My Application i have a table with multiple rows(Rows are Dynamically added to the table).First i am setting the table with the following properties:
width:900px;
height : auto,
Overflow : visible,
Max-height: : 200px.
If I use above properties,I'm getting a table with 5 or 6 rows(height upto 200px).After that i am getting the Vertical ScrollBar.
The problem is when a table has many columns, Vertical and Horizontal Scrolls are coming at the time of setting the table. The table height is not Increasing dynamically.
How can i use "height" property in CSS? (I want the table height to be increased when the columns are more.)
Thanks & Regards
Madhavi

Hey humble user. Errr I'm trying to understand what ur trying to do. U want to create a section of a region destructively from an existing region right? If so select the option convert to new region (opt-comm-R or selecting it by right clicking). Check your audio bin to make sure. Whats the "merge" function? Are u refering to the glue tool?

Finding Plant Creation and Updation Date

Hi all,
I just want to find out if it is possible to find out Plant Creation and Updation Date using ABAP statements. Does it get stored in CHDHR or CDPOS and if yes, then what is the object Key.
Thanks

Check Report RSVTPROT with table name T001W for Plant changes. I do not think it updated CDHDR.
You can SUBMIT this report and get back the list in your custom program.
How to get list back in your custom program refer
http://scn.sap.com/thread/3147016

Regarding : Delivering Plant Creation

How to create a new delivering plant in SD?
This value , we want to use while creating the a new customer , in the sales area data section.

Dear Mukesh,
Plants are getting created in to MM-Module
Path: SPRO --> IMG --> Enterprise Structure --> Definition --> Logistics-General --> Define, copy, delete, check plant --> Define plant
and are assigned to
1. Company Code (In Logistic-General)
Path: SPRO --> IMG --> Enterprise Structure --> Assignment --> Logistics-General --> Assign Plant to Company Code
NOTE: Alternatively, you may use, T. Code: OX18
AND
2. Sales Org + Dist. Channel ( In Sales and Distributioin)
Path: SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Sales Org -- Dist. Channel - Plant
You may also view Structure: Plant -> Sales Org./ Dist. Channel: Overview in T. Code: OVX6
Hope, this may help you.
Best Regards,
Amit

Regarding PO Creation for a new plant

Dear MM expets,
In IDES Version I have created a new company code, plant and done the necessary configuaration settings and assignments.
When I am trying to raise a PO, It is showing Earror message
"Account assignment mandatory for material XXXX"
Earror message no: ME062
Diagnosis:
" There is no provision for value based inventory management for this material type in this plant. Account assignment is thus necessary"
Please explain me, why im getting this message,
thanks in advance,

Hello Mr.Sairm,
Thanks alot for your answer, My problem got solved,
I have checked the customization checking for the material types,
In Quantity/Value updating field,
"By valuation area" is selected as default selection for both quanity and value,
Now I have selected "By valueation areas" for both quantity and value
Now my PO accepting me to raise a po for standard NB document type, without
asking any account assingment category.
Can u expalin me what exactly the difference between default setting and my present setting.
Any way once again thanks alot,
Can you give me your contact number?
Bye,
Govardhan,Vadlapatla.

STO ( stor. loc. to stor. loc of same plant ) creation frm Sales Order

Hello guys
I am facing a unique scenario in our current environment. Need you input ASAP
environment:
Org 1 - Plant 1 - division 1
Org 2 - Plant 2 - division 2
Org 1 wants to take over the sales of all the items belonging to division 2 which are currently being sold by Org 2.
These items are HAWA and their procurement is currently done outside ECC.
Now the procurement of these items will continue to be done by Org 2 & even its inventory will be owned by Org 2.
Proposed Sales Flow:
1) Org 1 accepts Order for the item with Plant as Plant 2
2) Plant 2 Delivers the goods to customer
3) Org 1 invoices the customer
4) Org 2 invoices Org 1 using Intercompany billing.
Now the challenge is wrt step 2.
The Items are shipped from Plant 2 with their Issuing storage location as ABC.
However these items are initially stocked in a different building outside the Plant 2 .. say stor. location = XYZ
Now based on the Sales Requirements due for shipment today .. the users will move the Inventory of the items from Stor. Location XYZ to ABC for which they want some reference document for the move (which I have recommended as STO)
I have come across some threads which give input regarding triggerring STO from Sales Order.
However my challenge is the STO in this case is between 2 storage locations ABC & XYZ of the same plant.
Do you think Sales Order triggering a PR (similar to 3rd Party scenario) & then this PR converts to a STO work ?
Please let me know the steps if possible.
THanks
Vin

Well actually the Selling Org ABCD is of a different Company code .. it is a typical case of Intercompany Sales .. where the Plant WXYZ is belonging to another company code.
I have setup the Intercompany Sales Process .. and want to trigger the Stock movement as mentioned above.
I have configured the STO for storage location - stor. location in a Plant. ...
However I am struggling to trigger a STO from a Sales Order.
I tried using the Schedule Lines to trigger a Pur. Req ... however the Supplying Plant field remains blank (which is the same in this case as it is a stock movement between 2 locations of the same plant).
The flow looks somewhat like this
Sales Order -
> Stock Transfer PR in Plant WXYZ -
> Delivery Doc for the STO --- > MIGO to receipt the inventory in 0001 -
> Delivery DOc for Sales Order -
> Invoice for end customer --- > Intercompany Invoice
If anyone has automated creation of a STO from a Sales Order .. please advice
Thanks
Vin

Regarding equipment creation..

Hi Genius,
Now I want some details about Equipment creation in PM module, and what r all the table comes... please send some link to learn equipment creation.

hi thanus,
This is vijay here, currently i m working with this epm module.
for equipment creation you will use ie01 for change ie02 and for display ie03.
some times you may be asked to create by regarding doccument no.
then go to j3gi.
well main fields are equipment no, recipient, sender, planning plant, maintenance plant, bussiness area, company code etc.
there r lots of table.
but usefull are
equi,faglflaxa,j_3gbelp,j_3gbelk,iloa,ITOB,EQKTX,IMPTT,IMRG,CKBS,CKIS ETC
REGARDS
VIJAY DWIVEDI
REWARDS IF USEFULL*
FOR ANY FURTHER INFORMATION U CAN GET BACK TO ME

Multiple plants creation is possiable with one Tcode in MM?

Hi All,
Is there any way to Create multiple Plants at once... like creating 500 Plants with one transaction code in MM? Don't want to use upload programme like LSMW.
Thanks in advance.
Shah Yan

Hi,
I dont think its possible to create multiple plants using a single T.Code. Since creation of Plant includes the maintenance of Address details.
Hence the only option you have is upload tools/programs such as LSMW.
Hope its clear.
Regards,

Plant Creation.

Hi All,
Can somebody provide me with a List of Steps for :
Creation of Plant, assignment, and all relevant settings related to that to be done in system for all standard scenarios in MM for that Plant (Like Creation of Master data , Quality Inspection, Goods Movement etc.). I hope my question is clear. I want only steps not Config. Docs please coz I am preparing a list of Steps involved. thanks in advance
regards,
Prashant Rathore.

Hi,
This steps may be useful to you :
Steps involved to create a new Plant in SAP.
OX14 - Define Valuation Area
OX10 - Create / Change / View Plants
OVXB - Create / Change / View Division
OX18 - Assign Plant to company code
OX19 - Assignment of company code to the Controlling Area
OB38 - Assign company code to Credit Control Area
OMJ7 - Assign business area to Plant/Valuation area and division
OMS0 - Assign Factory Calendar to the Plant and Business Area
Regards
Ram

Prerequisites for Plant Creation

Dear Friends,
What are the factors that determine for creation of a plant ?
Thanks in advance

Dear,
Factors to determin in creation of plant???
PLANT, is an organizational unit within logistics that subdivides an enterprise from the view points of production, procurement, and materials planning. A plant can be a:
o     Production facility
o     Distribution center
o     Regional sales office
o     Corporate headquarters
o     Maintenance location
If you are asking about how to create a plant:
IMG for SAP Plant Maintain
How to Configure a New Plant in SAP?
Plant 0001 is the SAP default provide for your reference.
OX14 - Define Valuation Area (Tick one only- Once your system go live, no more changes)
             Most company take the SAP recommended choice - Value Material Stock at Plant level
             Value Material Stock at Plant or Company Level
If you valuate material stocks at plant level, the plant is the valuation area.
If you valuate material stocks at company code level, the company code is the valuation area.
The decision you make applies to the whole client.
OX10 - Create / Change / View Plants
OVXB - Create / Change / View Division
OX18 - Assign Plant to company code
              e.g.       0001 - 0001 - All Plants
                                      Px1   - Plant Px1
                                      Px2   - Plant Px2
OX19 - Assignment of company code to the Controlling Area
OB38 - Assign company code to Credit Control Area
OMJ7 - Assign business area to Plant/Valuation area and division
             e.g. Plant Px1 - Business Area Bx1
                                                            Bx2
             Assign Valuation area to the Business Area
             .e.g. Valuation area Vx1 - Business Area Bx1
                                                     Business Area Bx2
OMS0 - Assign Factory Calendar to the Plant and Business Area
The plant plays an important role in the following areas:
Material Valuation - If the valuation level is the plant, the material stocks are valuated at plant level. Each plant can have its own material prices and account determination.
Inventory Management - The material stocks are managed within a plant.
MRP - Material requirements are planned for each plant. Each plant has its own MRP data. Analyses for materials planning can be made across plants.
Production - Each plant having they own production/planning.
Costing - In costing, valuation prices are defined only within a plant.
Plant Maintenance - If a plant performs plant maintenance planning tasks, it is defined as a maintenance planning plant. A maintenance planning plant can also carry out planning tasks for other plants (maintenance plants).
If you want to use the application PP (production planning) or product costing and job-order costing, you must set valuation at plant level.
The valuation level that you choose affects
the maintenance of material master records
the G/L accounts in which material stocks are managed
the G/L accounts to which transactions are posted in Materials Management
Effect on the maintenance of material master records:
Depending on the valuation level chosen,
you maintain accounting data in the material master record for each plant or for each company code
you define a valuation price for the material in each plant or in each company code
Effect on G/L accounts:
If material stocks are valuated at company code level, all plant stocks of a material are managed in a joint stock account for each company code.
If material stocks are valuated at plant level, you can manage the material stocks for each plant in different accounts. For each plant, you can define a separate determination.
If several plants are to use account determination, you can group these plants in "Valuation and Account Assignment" Customizing.
The plants will be created under Client- Company code level. Plant may have storage locations, assignmed purchase organizations, groups.
Regards,
Syed Hussain.
Edited by: Syed Hussain on Nov 5, 2008 5:03 PM

Problem regarding the creation of sales order using bapi.

Hai all,
I am creating sales order using bapi but i am, get following error messages :
TYPE ID NUMBER MESSAGE
E       VP   112       Please enter sold-to party or ship-to party
E       V4   219       Sales document was not changed
I have entered all the parameters.
my program is as follows :
*& Report ZSD_SALES_ORDER
REPORT ZSD_SALES_ORDER.
    Tables
*table definitions
TABLES:vbak,      "Sales Document: Header Data
        knvv,     "Customer Master Sales Data
        mara,     "General Material Data
        t001l,    "Plants/Branches
        mvke,     "Sales Data for Material
        vbap,     "Sales Document: Item Data
        konv.     "Conditions (Transaction Data)
    Types
*type for upload data
TYPES :BEGIN OF ty_upload,
       matnr(20) TYPE c,                  " Old material number
       quantity(20) TYPE c,               " Cumulative order quantity in sales units
VALUE TYPE       BAPIKWERT1,
      value(20) TYPE c,                  " Condition value
             value TYPE konv-kwert,                  " Condition value
END OF ty_upload.
*type for final output table
TYPES :BEGIN OF ty_main,
           bismt TYPE mara-bismt,    "Old material number
           matnr TYPE vbap-matnr,    "Material Number
           kunnr TYPE vbak-kunnr,    "customer number
           auart TYPE vbak-auart,    "Sales Document Type
           vkorg TYPE vbak-vkorg,    "Sales Organization
           vtweg TYPE vbak-vtweg,    "Distribution Channel
           spart TYPE vbak-spart,    "Division
           vbeln TYPE vbak-vbeln,    "Sales document
           werks TYPE marc-werks,    " Plant
           lgort TYPE mard-lgort,    "Storage Location
           posnr TYPE vbap-posnr,    "Sales Document Item
           parvw TYPE vbpa-parvw,    "Partner function
           kwmeng TYPE vbap-kwmeng,   "Cumulative order quantity in sales units
           kschl TYPE konv-kschl,    "Condition type
          kwert TYPE konv-kwert,    "Condition value
KWERT TYPE       BAPIKWERT1,
          kwert(20) TYPE c,    "Condition value
           waers TYPE konv-waers,    "Currency
     END OF ty_main.
*type for old material number
TYPES: BEGIN OF ty_matnr,
       matnr TYPE mara-matnr,
       bismt TYPE mara-bismt,
       END OF ty_matnr.
*type for order number
TYPES :BEGIN OF ty_output,
       vbeln TYPE vbak-vbeln,       "Sales Document
     END OF ty_output.
    Constants                Begin with C_                           *
CONSTANTS:
c_zpmu(4) TYPE c VALUE 'ZPMU',
c_zpmm(4) TYPE c VALUE 'ZPMM'.
DATA: c_ch(1) TYPE c VALUE 'X'.
    Data                     Begin with W_                           *
*global data for validations
DATA: w_count TYPE i,
      w_vkorg TYPE vbak-vkorg,
      w_vtweg TYPE vbak-vtweg,
      w_spart TYPE vbak-spart,
      w_werks TYPE t001l-werks,
      w_check TYPE c,
      w_itemno TYPE posnr_va,
     W_COND TYPE C.
      w_cond(3) TYPE c.
    Internal tables          Begin with IT_                          *
*internal table definitions
DATA : it_upload TYPE STANDARD TABLE OF ty_upload ,
       wa_upload TYPE ty_upload.
DATA : it_main TYPE STANDARD TABLE OF ty_main,
       wa_main TYPE ty_main.
DATA: it_matnr TYPE STANDARD TABLE OF ty_matnr,
      wa_matnr TYPE ty_matnr.
DATA : it_output TYPE STANDARD TABLE OF ty_output.
Internal table for BAPI.
DATA: it_bapisdhd1 TYPE STANDARD TABLE OF bapisdhd1,        "Sales and Distribution Document Header
      wa_bapisdhd1 TYPE bapisdhd1.
DATA: it_bapisditm TYPE STANDARD TABLE OF bapisditm ,       "Sales and Distribution Document Item
      wa_bapisditm TYPE bapisditm.
DATA: it_bapiparnr TYPE STANDARD TABLE OF bapiparnr,        "SD Document Partner: WWW
      wa_bapiparnr TYPE bapiparnr.
DATA: it_bapischdl TYPE STANDARD TABLE OF bapischdl,       "Schedule Lines
      wa_bapischdl TYPE bapischdl.
DATA: it_bapicond TYPE STANDARD TABLE OF bapicond,       "Communication Fields for Maintaining Conditions in the Order
      wa_bapicond TYPE bapicond.
DATA: it_bapiret2 TYPE STANDARD TABLE OF bapiret2,        "Return Parameter
      wa_bapiret2 TYPE bapiret2.
      Parameters              Begin with PR_                        *
*selection screen definition
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME .
PARAMETERS: pr_vkorg TYPE vbak-vkorg OBLIGATORY,
            pr_vtweg TYPE vbak-vtweg OBLIGATORY,
            pr_spart TYPE vbak-spart OBLIGATORY,
            pr_kunnr TYPE kna1-kunnr OBLIGATORY,
            pr_werks TYPE marc-werks OBLIGATORY,
            pr_lgort TYPE mard-lgort OBLIGATORY.
PARAMETERS: pr_auart TYPE vbak-auart OBLIGATORY,
           PR_AUGRU TYPE VBAK-AUGRU OBLIGATORY.
                        pr_augru TYPE vbak-augru.
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN BEGIN OF BLOCK blk2 WITH FRAME.
PARAMETERS : pr_file TYPE ibipparms-path OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk2.
      At selection-screen                                           *
AT SELECTION-SCREEN.
PERFORM f006_validate_vkorg.
PERFORM f007_validate_vtweg.
PERFORM f008_validate_spart.
PERFORM f009_validate_kunnr.
PERFORM f010_validate_werks.
PERFORM f011_validate_lgort.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pr_file.
*for f4 help----
PERFORM f003_f4_help.
      S T A R T   O F   S E L E C T I O N                           *
START-OF-SELECTION.
*for material ,quantity and value upload
PERFORM f001_upload_file.
*get data
PERFORM f003_get_data.
*for check the data
PERFORM f002_check_data .
PERFORM f004_process.
*for posting
PERFORM f005_posting.
END-OF-SELECTION.
      E N D       O F   S E L E C T I O N                           *
*&      Form f001_upload_file
      upload file
FORM f001_upload_file .
DATA : lw_fname TYPE string.
CLEAR lw_fname.
lw_fname = pr_file.
REFRESH it_upload.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = lw_fname
      filetype                = 'ASC'
      has_field_separator     = c_ch
    TABLES
      data_tab                = it_upload
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      OTHERS                  = 17.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT it_upload INTO wa_upload.
   wa_upload-value = ( wa_upload-value ) / 10.
   MODIFY it_upload FROM wa_upload.
ENDLOOP.
ENDFORM.                    "F001_UPLOAD_FILE
*&      Form f003_f4_help
      f4 help
FORM f003_f4_help .
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
      field_name    = ' '
    IMPORTING
      file_name     = pr_file.
ENDFORM.                    " f003_f4_help
*&      Form check_data
      text
FORM f002_check_data .
DATA: lw_lines TYPE i.
DESCRIBE TABLE it_main LINES lw_lines.
IF lw_lines LE 0.
    RETURN.
ENDIF.
SELECT a~matnr
         a~bismt FROM mara AS a INNER JOIN mvke AS b
               ON amatnr = bmatnr
               INTO CORRESPONDING FIELDS OF TABLE it_matnr
               FOR ALL ENTRIES IN it_main
               WHERE a~bismt = it_main-bismt.
IF sy-subrc = 0.
    LOOP AT it_main INTO wa_main.
      CLEAR : wa_matnr.
      READ TABLE it_matnr INTO wa_matnr WITH KEY bismt = wa_main-bismt.
      IF sy-subrc = 0.
        MOVE: wa_matnr-matnr TO wa_main-matnr.
      ENDIF.
      MODIFY it_main FROM wa_main TRANSPORTING matnr WHERE bismt = wa_main-bismt.
    ENDLOOP.
ELSE.
   MESSAGE e000(zmsd) WITH text-001.
ENDIF.
ENDFORM.                    "CHECK_DATA
*&      Form F009_validate_vkorg
      text
FORM f006_validate_vkorg .
CLEAR w_vkorg.
SELECT SINGLE vkorg
      INTO w_vkorg FROM tvko
      WHERE vkorg EQ pr_vkorg.
IF sy-subrc <> 0.
    MESSAGE e000(zmsd) WITH text-012 pr_vkorg.
ENDIF.
ENDFORM.                    " F009_validate_vkorg
*&      Form f007_validate_vtweg
      text
FORM f007_validate_vtweg .
CLEAR:w_vtweg.
SELECT SINGLE vtweg
       INTO w_vtweg FROM tvtw
       WHERE vtweg EQ pr_vtweg.
IF sy-subrc <> 0.
    MESSAGE e089(zmsd).
ENDIF.
ENDFORM.                    " f007_validate_vtweg
*&      Form f008_validate_spart
      text
FORM f008_validate_spart .
CLEAR:w_spart.
SELECT SINGLE spart
        INTO w_spart FROM tspa
        WHERE spart EQ pr_spart.
IF sy-subrc <> 0.
    MESSAGE e087(zmsd).
ENDIF.
ENDFORM.                    " f008_validate_spart
*&      Form F010_validate_kunnr
      text
FORM f009_validate_kunnr .
DATA: l_kunnr TYPE kunnr.
CLEAR: w_vkorg, w_vtweg,w_spart.
SELECT SINGLE kunnr FROM knvv
         INTO l_kunnr
         WHERE kunnr = pr_kunnr
         AND    vkorg = pr_vkorg
         AND    vtweg = pr_vtweg
         AND    spart = pr_spart.
IF sy-subrc <> 0.
   MESSAGE e000(zmsd) WITH text-010 pr_kunnr text-011 pr_vkorg .
ENDIF.
ENDFORM.                    " F010_validate_kunnr
*&      Form f010_validate_werks
      text
FORM f010_validate_werks .
CLEAR:w_werks.
SELECT SINGLE werks
        INTO w_werks FROM t001w
        WHERE werks EQ pr_werks.
IF sy-subrc <> 0.
    MESSAGE e088(zmsd).
ENDIF.
ENDFORM.                    " f010_validate_werks
*&      Form F011_validate_lgort
      text
FORM f011_validate_lgort .
CLEAR:w_werks .
SELECT   SINGLE werks FROM t001l
         INTO w_werks
         WHERE werks = pr_werks
         AND    lgort = pr_lgort.
IF sy-subrc <> 0.
    MESSAGE e000(zmsd) WITH text-007 pr_lgort text-008 pr_werks .
ENDIF.
ENDFORM.                    " F011_validate_lgort
*&      Form f003_get_data
      text
FORM f003_get_data .
CLEAR wa_main.
REFRESH it_main.
LOOP AT it_upload INTO wa_upload.
    CLEAR : wa_main.
    MOVE: wa_upload-matnr     TO wa_main-bismt,
          wa_upload-quantity TO wa_main-kwmeng,
          wa_upload-value     TO wa_main-kwert,
          pr_vkorg            TO wa_main-vkorg,
          pr_vtweg            TO wa_main-vtweg,
          pr_spart            TO wa_main-spart,
          pr_kunnr            TO wa_main-kunnr,
          pr_werks            TO wa_main-werks,
          pr_lgort            TO wa_main-lgort.
    APPEND wa_main TO it_main.
ENDLOOP.
ENDFORM.                    " f003_get_data
*&      Form f004_process
      text
FORM f004_process .
CLEAR w_check.
LOOP AT it_main INTO wa_main.
   IF wa_main-matnr = ''.
     WRITE:/ text-006,
                 wa_main-bismt.
     w_check = 1.
   ENDIF.
   IF wa_main-kwmeng = 0.
     WRITE:/ text-005,
             wa_main-bismt.
     w_check = 1.
   ENDIF.
   IF    pr_auart <> 'ZM01'.
     IF wa_main-kwert IS INITIAL.
       WRITE:/ text-004,
                wa_main-bismt.
       w_check = 1.
     ENDIF.
   ENDIF.
ENDLOOP.
ENDFORM.                    " f004_process
*&      Form f005_posting
      text
FORM f005_posting .
CLEAR: w_itemno,
         w_cond.
w_itemno = 10.
w_cond = 1.
IF w_check = '' OR w_check = 1.
wa_bapisdhd1-doc_type = pr_auart.
wa_bapisdhd1-ord_reason = pr_augru.
LOOP AT it_main INTO wa_main.
    IF w_cond = 1.
      CLEAR: it_bapiret2,
             it_bapisditm,
             it_bapiparnr,
             it_bapischdl,
             it_bapicond.
      REFRESH:it_bapiret2,
              it_bapisditm,
              it_bapiparnr,
              it_bapischdl,
              it_bapicond.
      MOVE: wa_main-vkorg TO wa_bapisdhd1-sales_org,
            wa_main-vtweg TO wa_bapisdhd1-distr_chan,
            wa_main-spart TO wa_bapisdhd1-division.
      wa_bapisdhd1-wbs_eleM = 'Y561.1'.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
        EXPORTING
          INPUT         = pr_kunnr
       IMPORTING
         OUTPUT        = pr_kunnr.
      wa_bapisdhd1-PURCH_NO_S = pr_kunnr.
      wa_bapisdhd1-PURCH_NO_C = pr_kunnr.
    ENDIF.
    MOVE: w_itemno TO wa_bapisditm-itm_number,
           wa_main-matnr TO wa_bapisditm-material,
          wa_main-BISMT TO wa_bapisditm-material,
          wa_main-werks TO wa_bapisditm-plant,
          wa_main-lgort TO wa_bapisditm-store_loc.
                       wa_bapisditm-target_qty = '10'.
    wa_bapisditm-PURCH_NO_S = pr_kunnr.
    wa_bapisditm-PURCH_NO_C = pr_kunnr.
    APPEND wa_bapisditm TO it_bapisditm.
    IF w_cond = 1.
      wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-itm_number = 10.
        wa_bapiparnr-partn_role = 'SP'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      wa_bapiparnr-partn_role = 'AG'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'RE'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'RG'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'WE'.
      APPEND wa_bapiparnr TO it_bapiparnr.
    ENDIF.
    wa_bapischdl-itm_number = w_itemno.
    wa_bapischdl-req_qty    = wa_main-kwmeng.
     wa_bapischdl-PURCH_NO_S = pr_kunnr.
    APPEND wa_bapischdl TO it_bapischdl.
    wa_bapicond-itm_number = w_itemno.
    wa_bapicond-cond_type = 'ZECL'.
     IF    ( wa_bapisdhd1-doc_type = 'ZPMU' ) OR ( wa_bapisdhd1-doc_type = 'ZPMM' ).
       wa_bapicond-cond_type = 'ZVAL'.
     ELSE.
       wa_bapicond-cond_type = 'ZMRP'.       "+PK12122006
     ENDIF.
    wa_bapicond-cond_value = wa_main-kwert.
    APPEND wa_bapicond TO it_bapicond.
    w_itemno = w_itemno + 10.
    w_cond   = w_cond + 1.
ENDLOOP.
data : SALESDOCUMENTIN like BAPIVBELN-VBELN.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      order_header_in     = wa_bapisdhd1
    IMPORTING
      salesdocument       = SALESDOCUMENTIN
    TABLES
      return              = it_bapiret2
      order_items_in      = it_bapisditm
      order_partners      = it_bapiparnr
      order_schedules_in = it_bapischdl
      order_conditions_in = it_bapicond.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = c_ch.
ENDIF.
LOOP AT it_bapiret2 INTO wa_bapiret2.
    DATA : w_err(100) TYPE c,
    w_matnr TYPE matnr.
    IF wa_bapiret2-type = 'E' AND wa_bapiret2-id = 'V1' AND wa_bapiret2-number = 392.
      UNPACK wa_bapiret2-message_v1 TO w_matnr.
      READ TABLE it_matnr INTO wa_matnr WITH KEY matnr = w_matnr.
      IF sy-subrc EQ 0.
        CONCATENATE text-013 wa_matnr-bismt INTO w_err SEPARATED BY space.
        MESSAGE w_err TYPE 'S'.
      ENDIF.
    ENDIF.
    IF WA_BAPIRET2-TYPE = 'S'. " Comment
      WRITE: 40 TEXT-009, WA_BAPIRET2-MESSAGE_V2+0(10).
    ENDIF.
ENDLOOP.
ENDFORM.                    " f005_posting
I have given all the necessary parameters. it is telling that error is in parameter
sales_header_in.
I have checked it.
i have assigned purch_no_s and purch_no_c of the structure BAPISDHD1(ORDER_HEADER_IN)
in the bapi with customer number.
and also i have assigned the partnumber of the structure BAPIPARNR ORDER_PARTNERS
in the bapi with customer number.
but still , it is diplaying the error message, please enter the sold to or ship to party number.
how to resolve this error.
this is urgent requirement.
points will be awarded.
thanking u in advance,
a.srinivas.

Hi,
Did u have a look at the standard programs which make use of BAPI_SALESORDER_CREATEFROMDAT1
Heres a list...
LWSSOU08
MV45WF0S
MWWMJF21_BAPI_SALESORDER_CREAT
RBUS2032
Regards,
Tanveer.
<b>Please mark helpful answers</b>

Regarding PO creation

hi can any one help me out in creating PO using the bapi bapi_po_create1
with reference to PR data.
can any one help me out in what the fields required to pass into the bapi to create PO

Hi Shiva,
In that Header Data is Mandatory,
Please pass required Header data :
Purchasing Document Number
Company Code
Purchasing Document Type
Deletion Indicator in Purchasing Document
Status of Purchasing Document
Date on Which Record Was Created
Name of Person who Created the Object
Item Number Interval
Vendor Account Number
Language Key
ISO code for language key
Terms of Payment Key
Cash (Prompt Payment) Discount Days
Cash (Prompt Payment) Discount Days
Cash (Prompt Payment) Discount Days
Cash Discount Percentage 1
Cash Discount Percentage 2
Purchasing Organization
Purchasing Group
Currency Key
ISO code currency
Exchange Rate
Indicator: Fixing of Exchange Rate
Purchasing Document Date
Start of Validity Period
End of Validity Period
Warranty Date
Quotation Number
Quotation Submission Date
Your Reference
Responsible Salesperson at Vendor's Office
Vendor's Telephone Number
Supplying Vendor
Customer Number 1
Number of Principal Purchase Agreement
Indicator: Goods Receipt Message
Supplying (Issuing) Plant in Stock Transport Order
Incoterms (Part 1)
Incoterms (Part 2)
Collective Number
Different Invoicing Party
Our Reference
Logical System
Item Number Interval for Subitems
Release Indicator: Purchasing Document
Release status
Country of Sales Tax ID Number
ISO country code for VAT registration number
Reason for Cancellation
Goods Receipt Reason Code
Regards,
Ram.

Regarding Thread Creation

Hello,
To create a thread in java there are two methods.
(1) by extending from thread class.
(2) by implementing runnable interface.
implementing runnable interface is the preferred method to create a thread because we still have the option to extend from any other class.
But does anybody know why java provides 2 methods for thread creation, why doesn't it provide only option 2 (i.e. by implementing runnable interface) when it is the preferred option.
Regards,
Sandy.

Though Runnable interface is preferred to create threads in Java,most programmers extends Thread class.As jschell would say, 'I am rather certain' that the opposite is true.
The reason behind of this is that you can have a clear logic of your code by using ThreadThat's not even true and it certainly isn't a reason to extend Thread rather than implement Runnable.
most of the system programming written in java used Thread class instead of Runnable interface .If you have some evidence on the point please produce it. The consensus of opinion on these forums has been the other way round for many years.

Regarding plant creation

Similar Messages

Maybe you are looking for