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.

Similar Messages

Finish date in process order

Hi all,
I have create a process order manually by giving shedulling type current date and schedulle margin key is set with no floats...Now in schedulled date the operation is completed today,but the finish date is shown as tomorrows date....Can i know where is the setting to get the finished date the next date of operation....(Float periods in SMK is kept zero)
Regards,
Joseph.

please go through the link for your answer
Re: How Basic start and end times are determined for a process order?
As perthe notes, The order finish date is set to 24:00.( means next day)
Edited by: Sundaresan . E. V on Sep 15, 2010 2:17 PM

Read Master Data for Process order status change (REL to CRTD)

I am unable to read master data and thus change the status of process order from REL to CRTD. (COR2)
The reason it says, error in BOM reading, Transport Requirement (TR) already generated.
Even after deleting the TR (LB02), the issue still exists.
Is there another way of changing the status or some more steps are needed for the TR deletion?
Thnx!
Abhi.

Order header Status-
REL Released
MSPT Material shortage
PRT Printed
PRC Pre-costed
BASC Batch assignment complete
BCRQ Order to be handled in batches
SETC Settlement rule create.
In the error log it gives-
Diagnosis
Transfer requirements have already been generated, so therefore the bill of material cannot be read.
System Response
The system does not execute the action.
Then I deleted the TR (LB02), but still I cannot reread the master data.
The MSPT was for only 2 materials out of 6 and there is no GMPS status.
There is prod supply area and control cycle used.
and the TR generated at order release.

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

Configuration data on sales order not update with idoc ORDERS05

Hi All,
I'm trying to post Inbound ORDERS05 to create a sales order with configuration data. In particular i'm using the messsage type ORDERS, process code J3AA (identification J_4A_IDOC_INPUT_ORDERS).
On the IDOC tree, segments E1CUREF,E1CUCFG,E1CUINS,E1CUVAL are correctly valorized.
It is creating the order but not updating the configuration data, can someone please let me know if there are other fields/Segments that need to be populated in order to get the config updated in the sales order ?
Thanks
Piergiorgio

Hi ,
I am facing similar issue ( Configuring data in orders idoc )
Please give your inputs if your successfully
Thanks,
Raghu..

Schedule Lines dates for sales order

Our goal is this: On the line item > Schedule Line tab there is the requested delivery date. In the details of that schedule line there are five different dates:
Delivery Date
Goods Issue Date
Loading Date
Material Aval. Date
Transportation Plan. date
We need to be able to put in the customers requested date that is in the future on this schedule line, but if the parts were to be recieved in earlier then the date they requested, then we would want the parts to ship out early automatically.
For Example: Customer Requested date is 01/31/08 and the parts are confirmed to come in on 01/31/08. The parts end up coming in on 01/20/08, so the next time the delivery list is run, we would like the parts to ship out right away.
Is there a way to do this?

Thank you for the quick response. I understand that we can use the reschedule report to manually monitor the product whether is comes in or not, but was hoping to achieve having a static date on the schedule lines of when the customer requests the parts, and then the delivery date that activates the MRP and ATP checks would be an earlier date. So when the parts come in, it would read from the delivery date.
Not sure if this is even possible, or if SAP standard for the schedule line dates is to how only one active date per schedule line.

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

Validity End Date for A012 relation not updated

Hi All,
I am working on SRM5.0 and the HR org structure is replicated from ECC to SRM via idocs. Now, for one particular user, who holds position in 2 org units, the HRP1001 table data is incorrect.
For one of the relations A012 between S-O, the end date shown is in the past. I checked the ECC tables for this employee and the A012 relation is valid till 31/12/9999. But, in the SRM system, this date does not get updated.
Due to this employee is not shown as an approver for that particular org unit.
Does anyone know how I can update this date?
Regards,
Ancy

One of the Org unit is under the other org unit. So, I updated the position with the relation to the higher org unit only. So in the SRM system, by default, the supervisor for this org unit is the supervisor for the lower org unit too, unless there is a new supervisor for the lower org unit.

Process Order Basic Finish Date and Scheduled Finish Date

Folks,
I have a requirement from the business to be able to update the Process Order Basic Finish Date and Scheduled Finish Date independently from each other.
In other words, update the Basic Finish Date and the Scheduled Finish Date cannot change or update the Scheduled Finish Date and the Basic Finish Date cannot change.
I believe the reason for this is to be able to use the Basic Date to maintain the ATP accurately and keep the Scheduled Date to mark when the order was originally due from the shop floor to be able to measure if orders are being completed on time or late.
I have worked in tnx OPUZ and had some success with other issues with these dates but I can't seem to make them work independently from each other.
Or does anyone have any ideas how to measure proces order performance to the production schedule?
Thank you for your help,
Greg

Rajesha, thank you for your reply but it doesn't solve my problem.
Let me restate my scenario:
I start a process order and both the basic and scheduled finish dates are the same, June 1.
At some point, shop floor tells me they will be late and cannot deliver until June 15.
I need to update a date in the system so the ATP and the MRP planning runs have correct information for promising customers, I will update the Basic Finish date with June 15.
I also need to keep the original June 1 date in order to measure the shop floor performance to the production schedule to measure how early or late the order was delivered. How can I keep the original finish date or how can I measure if a process order is early or late??
Thank you for your help,
Greg

Process Order Schedule Finish date before Schedule Start date

On rare occasions, the process order Schedule Finish date is before the Schedule Start date. This causes an error on the APO system when the process order is CIF to APO. Does anyone have any ideas how this occur?
Thanks.
Best regards,
Sandy

Rajesha, thank you for your reply but it doesn't solve my problem.
Let me restate my scenario:
I start a process order and both the basic and scheduled finish dates are the same, June 1.
At some point, shop floor tells me they will be late and cannot deliver until June 15.
I need to update a date in the system so the ATP and the MRP planning runs have correct information for promising customers, I will update the Basic Finish date with June 15.
I also need to keep the original June 1 date in order to measure the shop floor performance to the production schedule to measure how early or late the order was delivered. How can I keep the original finish date or how can I measure if a process order is early or late??
Thank you for your help,
Greg

GR Cost not updating as Target Cost for process orders

Dear SAPians,
We are facing an issue in Target Vs Actual cost reporting for process orders. We are creating a process order after cost estimate of that material and doing the confirmations for activity cost. After that, GR has been done for the finished goods of that process order. That GR entry is updating the Actuals values but not updating the Target cost. When I am checking the standard report KKBC_ORD, I am getting the following figures.
Cost Elemnt Text     |     Target Cost     |     Actual Cost     |     Target Vs Act
Inventory Chnge FG     |     0     |     1,472,205.60-     |     1,472,205.60-
Packing Matrl Cons.     |     1,148,142.37     |     1,252,752.68     |     104,610.31
Raw Material Cons.     |     60,463.91     |     50,688.29     |     224.38
Semi-Fin Matrl Cns.     |     181,934.68     |     367,959.56     |     186,024.88
Labour Cost Activity     |     39,735.36     |     39,862.80     |     127.44
Machine Cst Activty     |     41,611.75     |     43,153.01     |     1,541.26
That 'Inventory Change FG' entry is showing the GR posting updating actuals and not target cost. This is causing huge difference in target vs actual cost that will affect the profit and loss figures ultimately.
What am I missing here? What should I do to update the GR amount in Target cost as well.
Shirazi

Dear,
Target Cost on Production Order or Process Order is shown only when Variance is Calculated.
So please calculate the Variance, system will show the Total Target Cost.
Br,Vivek

Is there any method to stop rescheduling of the PO Need By date from ATP if there is any holiday specified in shipping calender. The requirement is to update the schedule ship date on Sales Order but the lead time of Purchase Order should not increase

We are currently not able to manage schedule ship date proposed by ATP when our warehouse is closed. For example , we would like that ATP doesn't propose any schedule ship date for the first of May , which is a non working day in France. The constraint is that we don't want our purchase need by date to be impacted by the process.
I tried to closed one day in FR1 calendar and, after testing with order management, it appears that ATP didn't propose the closed day, so that's fine, but, our purchase order lead time was increased of 1 day and this is not what we expected.
Can you help us to find the right process.
Thanks

Hi Sandeep,
when we try to Rescheduled out the PO and the request is errored out the with the error:-
Start of log messages from FND_FILE
reschedule fails
old date in planner workbench: 19-MAY-11
new date: 07-JUN-11
header: 417474
line: 605652
po number: 2049031859
shipment no: 1
The need by date/promised date in the source instance is not the same as the need by date/promised date in the destination instance.
In the source instance,
The need by date is 19-MAY-11, and the promised date is 19-MAY-11
End of log messages from FND_FILE
---------------------------------------------------------------------------

Updating Scheduling data for Purchase Order

Hi,
I need a function module which can update the scheduling data for purchase order in EKET table. Normally we create Purchase Order as a reference from purchase requisition through BAPI_PO_CREATE1. That time it takes care of all the scenarios. But as per the requirement I want to create a PO which is created from more than one Purchase Requistions so I can't use the said BAPI. But still I am using this BAPI and after creation is completed I am updating the Requistions. The same scenario is taken care in ME59N, but I can't copy that code because of some requirements. So could any one please give me the idea to replicate the same functionality with any function module or other ways.
Thanks
Somnath paul

try to pass all u sheduling related fields to POSCHEDULE and make sure u have enabled POSCHEDULEX along with sheduling related fields .....also (if no changes are there leave it with space )...
this will definetly update not only eket table ....it will update every table regarding to purchase order,ekpo,ekko,eket ...etc
Example of population of BAPI interface in the Function
Parameter: POHEADER
COMP_CODE            =                    1000
DOC_TYPE             =                    NB
ITEM_INTVL           =                    00001
VENDOR               =                    0000001000
PMNTTRMS             =                     0001
PURCH_ORG            =                     1000
PUR_GROUP            =                     001
CURRENCY             =                     EUR
Parameter: POHEADERX
COMP_CODE            =                     X
DOC_TYPE             =                     X
ITEM_INTVL           =                     X
VENDOR               =                     X
PMNTTRMS             =                     X
PURCH_ORG            =                     X
PUR_GROUP            =                     X
Parameter: POITEM
PO_ITEM              =                     00001
MATERIAL             =                    100-100
PLANT                =                    1000
STGE_LOC             =                    0001
QUANTITY             =                    15.000
TAX_CODE             =                    V0
ITEM_CAT             =                     0
ACCTASSCAT           =                    K
Parameter: POITEMX
PO_ITEM              =                    00001
MATERIAL             =                    X
PLANT                =                    X
STGE_LOC             =                    X
QUANTITY             =                    X
TAX_CODE             =                    X
ITEM_CAT             =                    X
ACCTASSCAT           =                    X
Parameter: POSCHEDULE
PO_ITEM              =                    00001
SCHED_LINE           =                    0001
DELIVERY_DATE        =                    02.12.2002
QUANTITY             =                    6.000
PO_ITEM              =                    00001
SCHED_LINE           =                    0002
DELIVERY_DATE        =                    03.12.2002
QUANTITY             =                    5.000
PO_ITEM              =                    00001
SCHED_LINE           =                    0003
DELIVERY_DATE        =                    04.12.2002
QUANTITY             =                    4.000
Parameter: POSCHEDULEX
PO_ITEM              =                    00001
SCHED_LINE           =                    0001
PO_ITEMX             =                    X
SCHED_LINEX          =                    X
DELIVERY_DATE        =                    X
QUANTITY             =                    X
PO_ITEM              =                    00001
SCHED_LINE           =                    0002
Parameter: POACCOUNT
PO_ITEM              =                    00001
SERIAL_NO            =                    01
QUANTITY             =                    15.000
GL_ACCOUNT           =                    0000400000
COSTCENTER           =                    0000001000
CO_AREA              =                    1000
Parameter: POACCOUNTX
PO_ITEM              =                    00001
SERIAL_NO            =                    01
QUANTITY             =                    X
GL_ACCOUNT           =                    X
COSTCENTER           =                    X
CO_AREA              =                    X
Parameter: POCOND
ITM_NUMBER           =                    000001
COND_ST_NO           =                    001
COND_TYPE            =                    PB00
COND_VALUE           =                    79.900000000
CURRENCY             =                    EUR
CURRENCY_ISO         =                    EUR
COND_UNIT            =                    KG
COND_P_UNT           =                    1
CHANGE_ID            =                    U
Parameter: POCONDX
ITM_NUMBER           =                    000001
COND_ST_NO           =                    000
ITM_NUMBERX          =                    X
COND_TYPE            =                    X
COND_VALUE           =                    X
CURRENCY             =                    X
CHANGE_ID            =                    X
Parameter: POPARTNER
PARTNERDESC          =                    OA
LANGU                =                    EN
BUSPARTNO            =                    0000001100
PARTNERDESC          =                    GS
LANGU                =                    EN
BUSPARTNO            =                    0000001200
PARTNERDESC          =                    PI
LANGU                =                    EN
BUSPARTNO            =                    0000001000
reward points if helpful....

Editing of scheduled dates in Process Order Operations

Hello,
I have a requirement, in which the client would like to change the Scheduled dates in the operation details of a process order.
In the header screen of a process order, if we change the basic start / finish dates (depending on forward or backward scheduling), and reschedule the process order, the process order is rescheduled, with the new dates.
The client's requirement is, they should be able to change the Scheduled dates in the tab "Operation - Dates", of the "Operation overview" screen, in a process order. Normally the field is not editable, and the system calculates the dates, based on the start / finish dates, entered in the process order header.
I would like to know, what is the way out, to meet this requirement.
Thanks.

Hi,
As every body else is explaining it is not possible for standard SAP , as of normal business or any business scenario why would a client want to change the operation dates from Production order ( still not understood.....)
There are two options to do that:
1) Copy the whole transaction ( programmes ) into some Z - transaction and in the programme you can change the object ( CO_VG_OPR_*) from being grayed out.
This will alllow you to change the dates.
2) you can go for enhancement with the following FM
BAPI_ALM_ORDER_MAINTAIN
I suggest you to clear these things with client.These things require more of ABAP work.
And as said changing the standard behaviour of the system can cause performance issues.
Please close the thread if satisfied.
prakash

Change of Basic Finish Date for a Maintenance Order

Hi Experts,
I have a requirement where I need to change the Basic Finish Date of an order. Currently in config for order type and plant combination, scheduling parameters are set as:
Adjust to Basic Finish Dates
Automatic Scheduling.
If in an order, I remove the tick for Automatic Scheduling, I am able to change that but I am not supposed to do that.
Can you suggest me how thisissue can be resolved. Remember, changing the Config is not an option.
Regards...

hi
Since you have done the adjust basic dates ,kindly change the operation dates ,which will automatically change the dates specified in the operation dates
regards
thyagarajan

Scheduled finish date for process orders not updating in BW

Similar Messages

Maybe you are looking for