Production orders not updated in Live Cache

Hi All,
We are currently facing a strange issue. Planned orders created in APO are converted into Production orders in R/3. When they are CIFfed to APO, those prodcution orders are captured in Product view but are not updated in either /SAPAPO/OM16 or Production list (/SAPAPO/PPL1). In these two transactions the production orders are not visible but their respective planned orders are showing up.
When delta report is executed for Production orders with "Consider Requirements/Receipts" as sub-object, these orders are captured with Error code 501 (Requirement/Receipt for the order exists only in R/3). When pushed to APO, these orders are updated in the Live Cache.
Can anyone share your thoughts on what could be the root cause for this issue.
Appreciate your thoughts
Thanks,
Sai

Thanks Vikas and Senthil,
Its not the issue with all the Production orders. The issue is with only few orders and we are in the process of tracing out the pattern.
Our Primary concern is that the orders captured in the delta report are visible in Product view even without taking any action in CCR but are missing in OM16. Its only after taking the action those orders are visible in OM16. I believe the data in the product view is read from Live Cache and the Live Cache contents are displayed in OM16. So, whatever orders visible in Product view have to be displayed in OM16 which is not happening.
Please let me know if I am missing anything.
Thanks,
Sai

Similar Messages

BAPI_GOODSMVT_CREATE for production order,not update database

hi guru,
i am using BAPI_GOODSMVT_CREATE for production order.When i m testing this BAPI
at se37 it creates one mat doc no and i m not getting any return messages.Now i m
writing code for it at se38. but it does not update the database even though i used
bapi_transaction_commit. here sy-subrc = 0.bt when i m checking MSEG table showing
that mat doc no does not exists.
please help me out asap.
thanks and regurds,
manasi

CHECK THIS CODE
REPORT ZBAPI_GOODSMVT_CREATE.
*DECLARING INTERNAL TABLE TO HOLD FILE DATA.
DATA: BEGIN OF itab OCCURS 0,
          text(200),
      END OF itab.
*DECLARING INTERNAL TABLE TO PASS FILE DATA.
TYPES: BEGIN OF tw_goodsmvt,
            pstng_date TYPE budat,
            doc_date TYPE bldat,
            material TYPE matnr,
            plant TYPE werks_d,
            stge_loc TYPE lgort_d,
            move_type TYPE bwart,
*            entry_qnt TYPE erfmg,
            costcenter TYPE kostl,
        END OF tw_goodsmvt,
        tt_goodsmvt TYPE STANDARD TABLE OF tw_goodsmvt.
DATA: lt_goodsmvt TYPE tt_goodsmvt,
      lw_goodsmvt TYPE tw_goodsmvt.
*declaring internal table of bapi structure.
DATA:s_goodsmvt_header LIKE bapi2017_gm_head_01,
     lt_goodsmvt_item TYPE STANDARD TABLE OF bapi2017_gm_item_create WITH HEADER LINE,
     lt_return TYPE STANDARD TABLE OF bapiret2 WITH HEADER LINE.
DATA:str_filename TYPE string,
     gm_code TYPE gm_code,
      v_head_count TYPE i VALUE 0,
      v_prev_count TYPE i VALUE 1,
      v_qnt TYPE string,
      v_dummy.
*selection screen
SELECTION-SCREEN BEGIN OF BLOCK bk with frame title text_001.
PARAMETERS:p_docdat TYPE bldat,
           p_pstdat TYPE budat,
           fname LIKE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK bk.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR fname.
*to provide F4 functionality.
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
    IMPORTING
      file_name    = fname.
* start of selection
START-OF-SELECTION.
str_filename = fname.
gm_code = '06'.
* to upload data
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename            = str_filename
      filetype            = 'ASC'
      has_field_separator = 'X'
      read_by_line        = 'X'
    TABLES
      data_tab            = itab.
*SPLITING DATA TO INTERNAL TABLES.
LOOP AT itab.
    IF itab+0(1) EQ 'H'.
      v_head_count = v_head_count + 1.
      IF v_head_count GT v_prev_count.
        PERFORM bapi_upload.
      ENDIF.
      SPLIT itab-text AT ',' INTO v_dummy
                                  lw_goodsmvt-pstng_date
                                  lw_goodsmvt-doc_date.
      s_goodsmvt_header-doc_date   = lw_goodsmvt-doc_date.
      s_goodsmvt_header-pstng_date = lw_goodsmvt-pstng_date.
      v_prev_count = v_head_count.
ELSEIF itab+0(1) EQ 'L'.
    SPLIT itab-text AT ',' INTO v_dummy
                                lw_goodsmvt-material
                                lw_goodsmvt-plant
                                lw_goodsmvt-stge_loc
                                lw_goodsmvt-move_type
                                v_qnt
                                lw_goodsmvt-costcenter.
* PASSING DATA TO INTERNAL TABLE TYPE BAPI STRUCTURE.
    lt_goodsmvt_item-material = lw_goodsmvt-material.
    lt_goodsmvt_item-plant    = lw_goodsmvt-plant.
    lt_goodsmvt_item-stge_loc = lw_goodsmvt-stge_loc.
    lt_goodsmvt_item-move_type = lw_goodsmvt-move_type.
    lt_goodsmvt_item-entry_qnt = v_qnt.
    lt_goodsmvt_item-costcenter = lw_goodsmvt-costcenter.
    APPEND lt_goodsmvt_item.
ENDIF.
v_prev_count = v_head_count.
ENDLOOP.
PERFORM bapi_upload.
*&      Form bapi_upload
form bapi_upload .
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
EXPORTING
    goodsmvt_header             = s_goodsmvt_header
    goodsmvt_code               = gm_code
*   TESTRUN                     = ' '
* IMPORTING
*   GOODSMVT_HEADRET            =
*   MATERIALDOCUMENT            =
*   MATDOCUMENTYEAR             =
tables
    goodsmvt_item               = lt_goodsmvt_item
*   GOODSMVT_SERIALNUMBER       =
    return                      = lt_return.
        PERFORM commit_work TABLES lt_return.
        CLEAR : lw_goodsmvt, s_goodsmvt_header.
        REFRESH: lt_goodsmvt[], lt_goodsmvt_item[].
endform.                    " bapi_upload
*&      Form commit_work
*       text
*      -->P_LT_RETURN text
form commit_work tables   p_lt_return structure bapiret2.
IF NOT lt_return[] IS INITIAL.
*error handling
loop at lt_return.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
   ID              = lt_return-id
   LANG            = sy-langu
   NO              = lt_return-NUMBER
   V1              = lt_return-message_v1
   V2              = lt_return-message_v2
   V3              = lt_return-message_v3
   V4              = lt_return-message_v4
IMPORTING
   MSG             = lt_return-MESSAGE
EXCEPTIONS
   NOT_FOUND       = 1
   OTHERS          = 2.
WRITE: lt_return-id, lt_return-message, lt_return-message_v1, lt_return-message_v2,
             lt_return-message_v3, lt_return-message_v4.
      CLEAR lt_return.
    ENDLOOP.
ELSE.
* commit work
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*   EXPORTING
*     WAIT          =
   IMPORTING
     RETURN        = lt_return.
WRITE: lt_return-id, lt_return-message, lt_return-message_v1, lt_return-message_v2,
             lt_return-message_v3, lt_return-message_v4.
      CLEAR lt_return.
endif.
endform.                    " commit_work

GR for Production Order, not updating Stock

Hi All,
Issue:
I am posting a GR for a production order, but the stock qty is not getting updated. I checked in MB51, i find the document being posted, but in MMBE the stock is not updated. In the system, there is 2 settlement profiles, one which allows settlement on material & the other only on G/L or Cost Center. I find this issue only when i create orders which have settlement receivers as G/L or Cost Center, also in MB51 i find that the sloc field is blank, even though it is maintained in the order & the same is seen when i receive via MB31.
Await your inputs as to where i need to check to resolve this issue.
Regards,
Vivek

Hi Prasobh,
I believe your pointing in the right direction. My suspicion is on similar lines.
A brief backdrop:
Order is created, whose settlement is to be done on a G/L acct, the settlement profile does not allow settlement onto material & hence in the GR tab, the GR non-valuated indicator is ticked. I manually ticked the GR indicator to post GR via MB31.
In MB51 i find the material document, but what is interesting is, the storage location field is blank, even though the order contains this value, which was later seen during MB31 posting as well.
But a similar order has been created in the legacy system with the same parameters as above & i find the stock to be updated.
So i suspect, it is something to do with the account determination, which is not allowing the quantity updation to take place, because of the GR non-valuated tick in the order header.
Hope i was able to put across the issue to you in a clear way.
Regards,
Vivek

Unable to delete Order does not exist in live cache but in table POSMAPN

Hi Experts,
We are facing an issue where purchase order is not available in live cache (which means no GUID) but exists in database table POSMAPN. We have tried to delete it using standard SAP inconsistent order deletion program and also using BAPI BAPI_POSRVAPS_DELMULTI but not able to delete it.
Can anybody suggest a method by which we can get rid of this order from the system.
Thanks a lot.
Best Regards,
Chandan

Hi Chandan,
Apologize me for taking your question in a wrong perspective. If you want to delete the same then you need to Re-CIF the order from ECC so that it would come and sit in Live Cache. Once done, try using the BAPI.
If you are not successful with the above approach try running the consistency report /SAPAPO/SDRQCR21 in APO system
so that it first corrects the inconsistency between ECC and APO (Live Cache + DB tables) and then use the BAPI to delete the PO.
Not sure if you have tried this way. If this does not solve your purpose you need to check SAP Notes.
Thanks,
Babu Kilari

Status of Prod Order not updated as delta - 2LIS_04_P_COMP

Hi all,
We are currently using 2LIS_04_P_COMP to update the data to BI. We have enhanced the DS to include the status of the prod order from table JEST. However it seems that this is not getting updated to BI server whenever prod order change its status. There is a delta queue when I see in tcode LBWQ and then I run the collective update in LBWE and then it will disappear from the queue which is correct. But when I see in RSA7, there is nothing and also I run the infopackage in BI server, it cannot get any data. Anybody has this issue before?
Many thanks in advance.
Regards,
Janet

The delta will only be captured if the Production Order actually changes. When a change is made to the status of an object in JEST, or JCDS, it doesn't register as a change on the object. Therefore, changes in Production Order status won't invoke a change on the source tables for Production Orders and therefore not get captured on the 2LIS_04_P_COMP or 0PRODORDER_ATTR DataSiources.
If you need to capture the changes in status for Production Orders, you will have to create a generic DataSource that is sourced by the JEST table and join it with the Production Order in BW.
Edited by: Dennis Scoville on Sep 17, 2009 8:16 PM

Production order Qty update-urgent.

Hi all,
I want a query that must not allow me to update the Qty in the Production order.Once production order created from the MRP,it should not allow me to update any Qty at the production orer level what should be query its urgent.
mona.
thanx in advance.

Hi Mona,
Query is only for report. It will not be the tool you are looking for this task.
The SBO_Transaction_Notification SP can be used instead. There are quite a few threads discuss this topic. Try search in the forum to find what you need.
Thanks,
Gordon

Production order not coming in MD04 list

Dear PP gurus,
In the PIR i have entered a qty lets say 20 for a month for a FG , when i run the MRP system generated planned order for dependent req. and which i converted into production order.(20 qty)
During confirmation in CO11, , the yield qty is 15 and rework is 5 .
Now for the 5 qty in rework, i have created manually a rework production order with a differnt order type for example (ZR01).
and confirm the same and done the GR for the 5 qty .
When I check the MD04 (stock req list ), In the avilable qty it is showing totao stock 20 ( 15 which i confirmed earlier and 5 which i confirmed against rework)
but it is not showing the manual production order which i created with diffenent order type . Is it correct?
else in the customization anything needs to be done so that this order type should also refelect in the MD04
pls help.
Regards
Adhish

Hi,
Once you confirm & receive the rework order, the inventory is updated as seen by you the stock is 20. So the rework order will not show up in MD04.
Only orders which are not delivered completely & not TECO or having any restricted processing status will show up in MD04.
Hope the above clarifies.
Regards,
Vivek

SAP Production Order not closing

Hi there,
I am running the COHV with Complete parameter in the background, and it does pick up several TECO orders from the past, like say from 2009 which are not closed but it does not process them to CLSD status.
I am seeing some entries in COHV, CO1P, COFC transactions - I picked a few randomly to check.
The order qty is not always equal to the delivered qty - Again a random test
The consumption qty on the components is not always equal to the required qty, which leaves reservation open - random check
Is all the above causing my order not to close ? where do I see the error log, when I try to close the order. I wrote the above issues based on my random check.
Thank you

Hi SAP Process,
When you run COHV to close the orders, you can see the log with the list of orders that have not been closed.
To see in detail what has happened you will need to check order by order.
Other option will we to evaluate each situation separatelly. You can check COGI, CO1P, see open reservations, check if you have TR or TO if you use WM, etc.. Once each situation is cleaned, you will be able to closed most of your production orders. It is quite common to create a custom report to make all these checks (COGI, TR/TOs, etc) and closed the orders.
Kind Regards,
Mariano

Production orders not to be considered during MRP run

Dear SAPeers,
i want to know how to ensure that open production orders are not considered during the MRP run.
the following is the scenario.
PIR for march after MRP run creates a planned order. this planned order is converted to production order. now this production order is processed but not completely confirmed and TECOed after a certain quantity has been produced.
now we delete the old PIR and create a new PIR in the next month. now we revoke the TECO status of the production order and run MRP. I want to know how to avoid MRP from considering the open production order and create planned order for the complete PIR quantity.
Thanks and Regards
Srinivasan

Srini,
what i am worried is shortfall of raw materials in case they were to open the production order in the current month after the planning has been done. how do we allocate raw materials for both the plan as well as the open production order?
Okay, you presumably had RM available for all of your production orders (and those RM were balanced by the reservations from the production orders). Now, you TECO the production order. In effect, any un-issued RM are now released and freely available for other orders/planned orders. Now you plan the following month. Those RM that were freed can and will be used for the new plan. Odd business process, but OK. Now, you re-open the production orders, and, yes, you will have a shortage unless you run RM MRP again. This is, ah, inconsistent with any business process I have ever seen.
The question that jumps to mind is, "Why re-open the old production orders at all? Alternatively, why were they TECOd in the first place?" If one knows that he intends to complete an order in production, one does not normally TECO the order, and then later reverse the TECO.
With respect to my name, I must unfortunately keep a low profile. Ever since I escaped from the mental institution, the thought-police have been hunting for me. I do not wish to be the recipient of any further electroshock 'treatments'.
Rgds,
DB49

Scheduled finish date for process orders not updating in BW

We are having problems with the scheduled finish date (GLTRS) for process orders. When the process order is already released, changes done in R/3 on the scheduled finish date will not result to a delta hence data in BW is not updated. Table AFKO, where data is coming from, is always updated with the changes though. 2LIS_04_P_MATNR is used in extracting the data.
Has anyone experienced the same problem? We are looking for possible ways on how to have a delta whenever there are changes on the process order even after it is already released.
Any help would be greatly appreciated...

Hi Donna,
If I've understood your problem correctly, you can increase the load frequency as Sriee has pointed out.
If you want latest data frequently and if you are on BI 7.0 then you can look at Real Time Data Acquisition(RDA)
Regards,
Tom.

Production order not settle correctly

Hello Guru,
PO70 in the closing steps showing the balance of production jobs that settled in the current month. Normally the account holds hundreds of records for thousands of dollars. February close had approximately 10 records for $.05.
1. How Can I check to make sure the settlement is working properly into account 5049000 which is Production Variance Clearing Account?
2. We had 5000 production orders settled in September, 2013 and only 1500 settle in February, 2014. What could have caused this? How can I reslove and go about this issue?
Thank you.

Hi Adelkunle
While running variance cycle or settling the production orders, are you getting any error messages. Check the logs.
Also from business point of view and also based on status of the active production orders, it is quite possible to have low number of production orders settling to variances, in the current period. I do not see any technical issues in this, unless I have no complete understanding of your issue, in which case, I wish if you can please elaborate more on the issue, on technical side.
Regards
Mustafa

Price in orders not updated by DTW

Hi experts,
I'm trying to update price in order lines with DTW 88.0.11
The DTW returns no error but the price is not updated.
During the DTW, I saw in the tab 'Target Data' of the step 5, the row 'price' with the new value.
Is there a good reason for the data not been updated?
Regards,
Francis

Hi Jim,
Thanks for your answer.
I've thought to use your solution if no better one.
But I would have to calculate this price after VAT. It's possible but no simple...
Best Regards,
Francis

Specific order not updated in MI

Hi,
I have a PM order for which no update (in description, operation or anything else...) that we do in R/3 PM can reach middleware. It's linked notification updates reach MI with no problem. All other orders update work just fine as well. Only this given order is not updated in MI.
I thought that it was F.M. MAM30_001_CHANGE that would be called to update it in middleware, but it is not used. What F.M. is used to update order in middeware?
Is there anybody that could give me a hint about my issue?
Thanks
Davy

This may be due to schedule line category in the sales order ->item level.
In t.code VA03, enter the sales order number. Then highlight line item and click on schedule lines for items button on the bottom. Find the schedule line category derived for the item under schedule line category column.
Then go to t.code VOV6. Select the schedule line that you found in the sales order and click on details button. Under transaction flow, you will find Req/Assembly field, which may NOT be checked in your case. If this field is not checked, then the requirement will not be passed to MRP.
If this is checked and still you dont see the details in MD04, then run report SDRQCR21 in SA38 and check again.
Regards,

Production order mass updation of components

Dear Friends,
My production order is created and partially confirmed, and now i want to directly insert some 100 components in components overview of CO02 screen.
please suggest any mass insertion or uploadinding method exists.
Or if any BAPI exists pls tell me.
Note: Dont suggest Order Change management
Thanking you guys in advance,
Reagards,
Kumar

Hi,
You can use BDC method for this requirement
Regards,
Sankaran

SAP Production order not closed, what are the negative effects

Hi there,
We are not closing the production orders. What would be the negative effects ? The orders are delivered, costed and Technically complete and all the teams are happy and no one is complaining. I also know we would need to close the production orders. But what is the effect of not closing the orders. Any thoughts ?
thanks

Hello
Similar qustions have been already asked in the past. Please read the threads below to understand exactly what happens when closing a production order:
closing production orders
completion of a production order
BR
Caetano

Production orders not updated in Live Cache

Similar Messages

Maybe you are looking for