Problem in Pur order Creation :

Dera All ,
I am creating Pur Order in Me21n
Here i am getting the error :
" for the R1 fiscal year variant, no period is defined for 21.03.2009 E "
what need to do for the Same?
Regards ,

Dear,
i Think u have maintain
R1 Shortened fisc.year Jan-Sep'94
for that one you have to maintain to maintain Number of Posting as 12.
T code OB29.
SPRO --> MM --> Financial Account(New) --> Fiscal Year And Posting Period --> Maintain Fiscal Year Shortend
Take Help of FI person
This may help u
Regards,
Pardeep malik

Similar Messages

BAPI - Problem in Sales order creation

Hi Friends,
I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
Code:
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
Regards,
Dinesh

what messages u are gettting in RETURN ? Please check the RETURN tables data.
[code]CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
EXPORTING
sales_header_in = header
sales_header_inx = headerx
IMPORTING
salesdocument_ex = v_vbeln
TABLES
return = return
sales_items_in = item
sales_items_inx = itemx
sales_schedules_in = lt_schedules_in
sales_schedules_inx = lt_schedules_inx
sales_partners = partner.
Regards
Prabhu

Problem in process order creation.

Dear Sir/ Madam
i am facing a problem while process order creation.
the problem is:
Error when calculating cost for order ATFEDEC11 "see log Log is deleted when saving
Do you still want to save?"

Hi,
The log for production order preliminiary costing is not saved. Therefore, once the order is saved, there is no log available anymore (this is by the way a question of PP; none of the logs is saved).
Hope that helps...
Regards,
Declan

Problem with Sales Order Creation

Hi,
In my sales order creation program if item qty is zero, it should not include that item in the order. It is not working properly with this example it is creating same order for customer 1001 and 1004. It is checking for qty = 0 condition and executing 'continue' statememt , then it is not checking 'At end of kunnr' and creating only one order for all the remaining 4 items from 1001 and 1004 other than 0 qty's.
kunnr   matnr   qty     order#
1001     51038     723     102255
1001     51054     0
1001     51055     0
1004     51038     207     102255
1004     51054     236     102255
1004     51055     219     102255
it should create like this.
kunnr   matnr   qty     order#
1001     51038     723     102255
1001     51054     0
1001     51055     0
1004     51038     207     102256
1004     51054     236     102256
1004     51055     219     102256
Please help me fix this.
Thanks,
veni.

Hi,
Here is the code.
WHEN 'ORDERS'.
      DESCRIBE TABLE gt_zprice LINES lv_cnt.
      DO lv_cnt TIMES.
        lv_index = sy-index + 4.
        READ LINE lv_index FIELD VALUE chbox.
        IF chbox = 'X'.
          READ TABLE gt_zprice INTO gs_zprice1 INDEX sy-index.
          IF sy-subrc EQ 0.
            gs_zprice1-index = sy-index.
            APPEND gs_zprice1 TO gt2_zprice.
            CLEAR gs_zprice1.
          ENDIF.
        ENDIF.
        CLEAR chbox.
      ENDDO.
      gt4_zprice[] = gt2_zprice[].
     SORT gt4_zprice BY kunnr vtweg.
      LOOP AT gt4_zprice INTO gs_zprice1.
        IF gs_zprice1-crmemo IS INITIAL.
          AT NEW kunnr.
            MOVE 'Y' TO lv_flg.
          ENDAT.
          IF lv_flg EQ 'Y'.
            PERFORM headerdata.
            PERFORM texts.
            CLEAR lv_flg.
          ENDIF.
          IF gs_zprice1-eohqty IS INITIAL.
            CONTINUE.
          ENDIF.
          PERFORM itemdata.
          APPEND gs_zprice1 TO gt3_zprice.
          CLEAR gs_zprice1.
          AT END OF kunnr.
            PERFORM call_function.
            PERFORM update_pricetable.
            PERFORM errorcheckandcommit.
            REFRESH gt2_zprice.
            CLEAR chbox.
            REFRESH partner.
            REFRESH item.
            REFRESH itemx.
            REFRESH lt_schedules_in.
            REFRESH lt_schedules_inx.
            REFRESH conditions1.
            REFRESH order_text.
            lv_itemno = 10.
          ENDAT.
        ELSE.
          REFRESH gt2_zprice.
          CLEAR chbox.
        ENDIF.
      ENDLOOP.
      WRITE: /01(179) sy-uline.
      PERFORM headings.
      WRITE: /01(179) sy-uline.
      PERFORM displaydata.
ENDCASE.
Thanks,
Veni.

Problem in purchase order creation.

Hi,
during the creation of a PO with trx ME21N the system generates the following error:
System error in routine <b>FI_TAX_CHK_PRICING_DATA error code 13</b>How can I solve the problem?
Yours truly

Hi,
Check the pricing procedure in the purchase order. Check the condition type of the attached or not in the Calculation procedure and the corresponding Transaction Key is maintained or not.
Satya

Pricing problem in sales order creation

Hi friends,
         My requirement is to create sales order with ref to contract i am using 'BAPI_SALESORDER_CREATEFROMDAT2' , and I am extracting data from konv table to get price through condition record , but i am getting 4 messages
(S)    SALES_HEADER_IN has been processed successfully
(E)   Condition PR00 is not allowed as header condition
(W) The sales document is not yet complete: Edit data
(E)   Sales document was not changed
and i am not getting pricing for created sales order document.
please help.
regards,
Sravani.

hi
ZK01 Company Selling Price - 21.86 INR 1 BT - 2360.41 INR for 108 BT( your statement)
This is wrong 21.86 x 108 = 2360.88 and not 2360.41 as written by you
so the calculation of the system is correct
21.86 x 108 =2360.88
1.41 x 108 =153.28
So total 23.27 x 108 = 2513.16 (also 2360.88 +152.28 also is equal to 2513.16 )
you can check in calculator
If ZK01 is showing a wrong vaule 2360.41 instead of correct 2360.88 in your case then you need to check the configuration of that condition type
The subtoatal valuew hich you have written is also wrong because of ZK01
Problem lies in ZK01 check the other controls and rounding profile etc of ZK01 in V/06
Regards
Raja

Problem in Sales order creation BDC

Dear ABAPers,
I have Developed the BDC For VA01 Transaction code.While creating the Sales order it automatically creates the Serial number.But in BDC i am getting the Error message 'Serial Number is Being Created for the Material'.I am getting this message only for few serial numbers.What could be the Problem.
Thanks & Regards,
Ashok.

Hi
U chk ur recording..Because that serail number autamitacally picking or u are record that serial number.According to ur recording only uhave prepare ur flat file.
Better u condiser ur FUnctional consulatant.
Note:
When ever u record the BDC program u must sit with Functional consulatnt. Otherwise problem with u only.
Regards:
Prabu

Problem with internal order creation using BAPI_INTERNALORDER_CREATE. Help!

Hi Experts,
I am facing a strange problem in SAP. I have a scenario where I am integrating a .Net application with SAP R/3 via SAP XI.
The .Net application is calling XI web service via SOAP adapter. The XI then sends the data to the SAP R/3 system via RFC adapter.
XI calls the BAPI u201CBAPI_INTERNALORDER_CREATEu201D to create a new internal order in the R/3 system.
This scenario works perfectly fine when tested via XIu2019s runtime workbench or any SOAP or web service testing tool. New internal order gets created in the R/3 system without any issue. But when I test the same via the .Net application I found that the order is getting created properly but some fields like currency and cost center are disabled or grayed out in change mode. Have you encountered this problem earlier? Any clue what could be the root cause?
Please help!
thanks
Gopal

Hi Sampanth,
I think you did not understood my scenario. In real time or production situation I have to use .Net application to send data to XI. The XI will then send the same to R/3 system to create the internal order.
The .Net code is calling the XI's webservice using C# code and sends the data as a SOAP request.
How can .Net code grayout some fields in SAP R/3 system? Can you elaborate on what are you trying to explain?
Thanks
Gopal

Problem in production order creation

Hi All,
I am using BAPI "BAPI_PRODORD_CREATE" for creation of production orders. But if i pass the value to the BAPI, i am getting the error WBS Element does not exist always...
But if i give the same value in SE37 directly the BAPI is creating Production orders........But program level it is not working.......Please help me
Even i used for converstion level FM before passing the value to BAPI structure i.e "CONVERSION_EXIT_ALPHA_INPUT"
NOTE: this BAPI not require for COMMIT......
Thanks & Regards
Santhosh

Hi,
Check [this|Re: About BAPI_PRODORD_CREATE; forum.

Problem during Process Order creation

Hi,
I have problem while creating Process Order.
I have maintained all the basic data required to create the process order.
When I Release the order, I am able to create the control recipe also, but PI sheet is not generated along with it. System gives the message "No PI maintained in customising for CRD for which control recipe is to be generated "
If I maintain the same, then system is unable to create the control recipe.
What may be the problem here? What i can do to rectify this situation?
Pavan

Hi Pavan,
1. Maintain PI in SPRO of process management
2. Assign this PI to one of phse in master recipe
3. Plz check wheather ur created Control receipe destination or not.
4. if not then maitain the same in Spro.
5.Check the ordre type dependent parameter i.e COR4 from SPRO
see the Control recipe gerated in REL phse else maintai the asme in production scheduling profile.
if possible plz send the sctren shot fir the same to
[email protected]
Regards
Siddhesh

Problems in production order creation!!

Hello SAP experts, how are you , i have a question , can i configure the system to run the batch determination and then the ATP when i create a production Order with the CO01??, is there some option in spro to do it?.
Kind Regards.

German,
Follow path SPRO- IMG- Production - Shop floor control- Master data--- Define production secheduling profile T code OPKP.
Go into details of plant & prod. scheduling profile combination.
Under batch management, for 'Automatic batch creation in order' either select 1 or 2 as per your requirement.
Hope this helps you.
SmanS

Problem in Sales Order Creation with reference to Contract

Hi All,
We had enhanced Contracts (VA41) by adding fields thru append structures in VBAP and the same is provided in the "Additional Data B" tab at the item level.
The Z fields are populated with data and gets saved along with the contracts line items.
But when a sale order is created with reference to a contract, the data in the Z fields (maintained in Append Structures) of the contract are not getting copied to the line item of Sales orders.
Should a routine be necessarily written for copying Z fields from contract to Sales orders or Copy control must be set up for Z fields separately?
Any info on this would help.
Thanks,
K.V.Venkatasubramanian

Hi VJ,
The copying from Contract to Orders worked. I copied the standard routine (151) in data transfers and added the code to transfer Z fields from work area CVBAP to work area VBAP and attached the same in the copy control. It works!!!
Thanks for the help VJ.
Cheers,
Venkat

Problem in Sales order Creation

Dear Group,
While creating sales order with MTO senario by using material master strategy group as 20 i am getting the following error.
ERROR
Receiver categ. is not allowed by settlement prof. SD1 for this sender
Message no. KD031
Please guide me how to proceed further.
Thanks
Tamil

Hi
Please find the below link
Receiver categ. is not allowed by settlement prof. SD1 for this sender
Hope this will helps you
Dasaradha

Problem with Purchase Order creation with Random numbers .

Hi Experts
Currently i am facing an issue with Bapi BAPI_PO_CREATE1 to create Purchase order with random numbers for example items 1, 3,5.
Please let me know the settings .
Thanks in Advance

Hi Neha,
A reset of the release strategy only takes place if
- the changeability of the release indicator is set to '4' in
   case of a purchase requisition and '4' or '6' in case of
   another purchasing document (purchase order, request for
   quotation, contract, scheduling agreement),
- the document is still subject to the previous release
   strategy,
- the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
Review the SAP note 365604 and 493900 for more
information about Release strategy.
Regards,
Ashwini.

PROBLEM IN PUR.ORDER HISTORY

DEAR CONS
i CREATED A SERVICE P.O & SERVICE ENTRY SHEET. I released this service entry sheet. every thing is o.k.But in p.o history sevice entry no. is not coming. pl. solve this problem.

Hi,
Check whether it is successfully processed and once check for which line item u have done service sheet.
Thanks'
suresh

Problem in Pur order Creation :

Similar Messages

Maybe you are looking for