Bapi for sfg dependent dem,snp planned order qty, and ppds planned orde qty

Hi Gurus,
I am not much familiar with APO, so please help me,
Input details:
Field                         Value
Planning Version     000
Source Location *     1001     Single/Multi Value
Product *                          1000061     Single/Multi Value
Production Planner *     PRC     Single/Multi Value
Start Date *
End Date *
o/p:
Source Location     Date     Semi-Finished Material     Material Description     SFG Dependent Demand     SNP Planned Orders qty     PPDS Planned order Qty     Total SFG Variance due to Lot size     Total SFG Variance reference to dependent demand
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT     340     412     420     8     80
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT
Is there any bapi to fetch the data as shown in o/p.
Thanks

Hi Phani,
Tryout the below BAPIs
IF10503 (object)
BUS10503
Regards
R. Senthil Mareeswaran.

Similar Messages

Unable to convert SNP planned order to PP/DS planned order in RRP3

Hi,
This is an in-house production scenario. SNP planned order are created based on forecast, now i want to convert those SNP planned orders to PP/DS planned orders in product view. While converting i am getting the following error message.
Conversion canceled with error
Message no. /SAPAPO/RRP707
I have checked the SNP, PP/DS PDS, it looks good.
Regards,
LV

Hi Lingaiah,
Conversion SNP -> PP/DS SAP002 is scheduling heuristic
Heuristic for Conversion SNP->PP/DS as SAP_SNP_SNGL used for order conversion.
Regards,
R.Brahmankar

Planned order is creating before planning bucket for a specific material.

Planned order is creating before planning bucket for a specific material.
Eg: Planning Bucket future: 12 months & Start date- 01/02/2012, but Planned order Availability/Requirement date is 12/23/2011.
What causes this, how to fix it? Please suggest u2026
Thanks
Ravi

Since your planning bucket start date is in the future, so this is normal that the system is trying to satisfy the demand in jan2012 bucket by creating a receipt on Dec23, 2011.
Reasons for RECEIPT to be generated earlier is
(1) There might be a FIRM HORIZON( SNP PROD HOR)
OR
(2) There might be a GR time and the system is considering that time
In Customizing for Advanced Planning and Optimization -> Supply Chain Planning -> Supply Network Planning (SNP) -> Basic Settings -> Maintain Global SNP Settings, in the SNP:GR for Plnd Ords field, you have selected Processing Time.
Blank out these times and see if it works, else do one of the following:
(1) Set Period Factor(LOT SIZE TAB of PRODUCT MASTER) to 1, so that the receipts get created at the end of the bucket.
OR
(2) Create your demand at the end of the planning bucket period
Thanks
Kumar

Handling Planned order created from Demand planning and Sales order in MTO

Hi all
In MTO\ Repetitive we genrate Dependent requirement from demand planning (PIR) after running MRP which finally planned order created but on the other hand in short term we have Sales order which generate planned order after running MRP(In MTO), How we should handle planned order generated from Demand planning and the ones generated from sales order.(both after MRP Running).
Regards
Babak Bolourchi

Dear,
You can combine the planning strategy also main as 56 and second as 65 and in demand managment MD61 you have the option select requirement type.
Then while creating sales order use MTO strategy and take MRP run through MD50 and then MD02.
and if you want to assign the stock to sales order then you and do it through MB1b with 412 E movement type.
As per my knowledge, generally 56 strategy only takes Sales Order Stock into consideration.
Consider setting the Individual/Collective indicator to 2.
Mark those characteristics that should have a usage probability in demand management as Relevant for planning.
Hope clear to you.
Regards,
R.Brahmankar

Costing affect with MRP at planned order level and after production order

Dear all,
How the costing affect with MRP at planned order level and after production order completion?
Edited by: Maulik on Jun 24, 2009 1:59 PM

Dear Maulik,
check Mr. Vinod's inputs abt costing
1. Maintain following master data:
MM01 Material Master with Costing and accounting view. Make sure all the cost Std, Moving avg etc is maintained along with valuation class in Accounting view 1. In costing tab pls make sure "with qty structure" and "Material Origin" are ticked.
CS01 BOM with components marked with costing relevance in Status/Long Text Tab. Also check all the qty are correct.
CR01 Work Center in Basic data tab maintain standard value key sau SAP1 and in costing tab maintain the workcenter, activity type and formulas (Usually standard formulas like for Machine Hours SAP006, Labour SAP007, Setup Activity SAP005 is used).
KL01 Cretae activity types, in basic data tab maintain ATyp Category AS "1" and cost element (as provided by your FI Guy).
KP26 Activity pricing, here with the combination of Activity type and the cost center you assign price to the activity.
2. SPRO Activity
Maintain Costing sheet IMGControllingProd cost controllingProd Cost PlanningBasic settingoverheadsdefine costing sheet.
OKKN Define costing variant, you define costing type (In the costing type, you define the purpose of a material cost estimate by specifying, for example, which field in the material master record the costing results can be transferred to like std price, moving avg etc), Valuation Variant (defines how the prices are prioratized), date control and transfer structure.
3. Costing Process Flow:
1. CK11N CREATE COSTING RUN
2. CK24 CREATE PRICE UPDATE (You Mark and release the prce to be updated)
4. COSTING VARIANT WRT PP
1. OPL1 DEFINE COSTING VARIANT WRT PP
2. OKK4 or OPN2 DEFINE VALUATION VARIANT
3. OKK1 or OPM1 DEFINE COSTING TYPE
4. OPL8 ORDERTYPE DEPENDENT PARAMETER (assign the above creted costing type for both planned and actual)
Hope this will throw some light on product costing.
Regards
kumar

Firm Planned order List out side Planning Time Fence

Dear Gurus
I have the following requirement.I need to get the list of Firmed Planned order list for my plant, which are the out side of Planning Time Fence.I tried by md19 but it did not give me any list like that.Any urgent solution is appreciated .
Regards
Jia

My requirement is planned order list beyond the planning time fence.In PLAF table we have option to give the firming indicator YES/NO .But while giving the date rage I have difficuly.We have several material which are planned in various plannig time fence and there is no fixed date range.There may be one material planned 21/04/08 to 25/04/08.At same time other material may be having 30/04/08 to 5/05/08 .So we cant give any fixed date range to segregate the firmed planned order out side the date range.
You soultion is appreciated
Regards
Jia

Planned order number and Plnkn

Dear All,
I need the table link between planned order number and Number of the task list node(PLNKN).
Thank you in advance
Regards
Sailendra.M
Edited by: nivedita yadav on Jun 25, 2010 2:35 PM

Dear Nivedita,
Check with this functional Module in SE37
BAPI_PLANNEDORDER_GET_DETAIL
In my understanding I dont think nwe can get this data from table.
Regards
S Mangalraj

SNP Planned order start and end dates are not calculated correctly

Hello SNP Guru's
The SNP planned orders generated after the Heuristics run, have a start and end date based on the Activity Duration (Fixed), while the resource consumption is based on the Bucket Consumption (Variable), which is correct.
The Activity Duration (Fixed) is based on the BOM Base Quantity. So if the Activity Duration = 1 day, and if the order quantity is more than a day, the start and end dates, still shows as 1 day. So no matter what is the order quantity, the start and end dates is always = 1 day.
Does anyone have any experience in implementing any code to change the start and end dates on SNP Planned Order?
Seems like it should work as standard.
Am i missing something?
Thanks,
Mangesh

Dear Mangesh,
SNP is a infinite planning tool. If you have defined fixed duration to be 1 DAY in the activity, no matter how many quantity you input for your planned order, the order will last for one day. If the resourced is overloaded, you then run capacity levelling to
banlance the capacity. What your expected beahavior happens in PPDS planning.
Claire

BAPI for Reversal of Goods Receipt Purchase Order(Transaction : MIGO)

Hi all,
Is there any BAPI for the Reversal of posting the documents Goods receipt Purchase order
(Transaction: MIGO).
Any inputs on this..is highly appreciable...
thanks in advance...
regards..
prathima.

Hi,
Try this passing material doc and year.
* Cancel the goods movement (creates a reversal document)
CALL FUNCTION 'BAPI_GOODSMVT_CANCEL'
    EXPORTING
      materialdocument = g_material_doc
      matdocumentyear = g_matdoc_year
    TABLES
      return           = i_return.
Edited by: Raj on May 14, 2008 7:46 PM

BAPI for Characteristic Dependency

Hi Friends,
We need to maintain the Characteristics & their dependency in each client as it is Master data. As per my knowledge we can use to create them through Mass upload like LSMW, BDC or BAPI. Since the data is very huge, is there any way to do.
When I was checking u201CBAPI_CHARACT_CREATEu201D , I couldnu2019t find there is option for Dependency upload. Is there any other BAPI for this.
Regards,
Sai Krishna

Hi Sai,
For each characteristic you need to assign dependancy separately and also if a charactistic is having multiple values, there also you need to assign dependancies separately. This is standrad behaviour.
As on date there is no BAPI or any other method to assign single dependacy to multiple characteristics or values at a time.
but this can be achived without using dependancy editor. Write a z-program for additional data so that only those fields can be displayed which are required after one single field( single characteristic). It will be out of dependancy editor and separate program. for this you may use function module BAPI_DOCUMENT_GETDETAIL2.
Hope this will help.
Regards,
Ravindra

Bapi for getting work center using receiving order and operation.

Hi Abapers,
could you tell me the name of bapi which takes receiving order , operation
and giving back work center
Thanks in Advance.

Hi,
Try this one Data_Sales upload
Bye

BAPI FOR Deleting a Schedule Line Item from EKES and EKET tables

Dear All,
I would like to for deleting one of the line item from EKES (Po Confirmation ) and the respective line item from the EKET(PO Schedule Line Item Table).
Assume that am allowing the user to select the lineitem from zprogram screen and collecting the PO and Its LIne Item details in an internal table.
Can i Use
<b>BAPI_PO_Change</b> , if so , can anybody tell me the steps to follow to use this bapi for deleting the PO lineItems, since i m going to try BAPI for First time.
pls help me out
Message was edited by: Raja K.P

Hi raja ,
loop at iekko1.
    w_index = sy-tabix.
    item-po_item   = itemx-po_item   = iekko1-ebelp.
    item-quantity = iekko1-mng01.
    itemx-quantity = iekko1-mng01.
    if iekko1-wamng = iekko1-wemng.
    itemx-no_more_gr = item-no_more_gr = 'X'.
    else.
    itemx-no_more_gr = item-no_more_gr = ''.
    endif.
    append item.
    append itemx.
      clear return[].
      call function 'BAPI_PO_CHANGE'
           exporting
                purchaseorder = iekko1-ebeln
           tables
                return        = return
                poitem        = item
                poitemx       = itemx.
      if return[] is initial.
      commit work and wait.
      call function 'DEQUEUE_ALL'.
search for deletion fields which u have to mark 'X'.
before calling this BAPi u have to lock the PO by using ENQUEUE.
<b>
FU BAPI_PO_CHANGE
Text
Change purchase order
Functionality
Function module BAPI_PO_CHANGE enables you to change purchase orders. The Change method uses the technology behind the online transaction ME22N.
Alternatively, the IDoc type PORDCH1 is available. The data from this IDoc populates the interface parameters of the function module BAPI_PO_CHANGE.
Functionality in Detail
Authorization
When you create (activity 02) an Enjoy purchase order, the following authorization objects are checked:
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can use your own parameters in the associated X bar (e.g. PoItemX) to determine whether fields are to be set initial, values inserted via the interface, or default values adopted from Customizing or master records, etc. (for example, it is not mandatory to adopt the material group from an underlying requisition - you can change it with the BAPI).
Transfer
Purchase order number
The PurchaseOrder field uniquely identifies a purchase order. This field must be populated in order to carry out the Change method.
Header data
The header data of the Enjoy purchase order is transferred in table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the tables PoItem (general item data). Changes regarding quantity and delivery date are to be made in the table PoSchedule.
Use the table PoAccount to change the account assignment information.
Services and limits
Changes to existing items cannot be carried out with the Change method. It is only possible to create new items.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. A new price determination process can be initiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor address in the table PoAddrVendor and the delivery address in the table PoAddrDelivery can only be replaced by another address number that already exists in the system (table ADRC). Changes to address details can only be made using the method BAPI_ADDRESSORG_CHANGE.
Partner roles
You can change all partners except the partner role "vendor" via the table PoPartner.
Export/import data
Export/import data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items. Changes to the export/import data of existing items are not possible.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText. Texts can only be replaced completely.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
If the PO was changed successfully, the header and item tables are populated with the information from the PO.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Restrictions
With this function module, it is not possible to:
Create subcontracting components (you can only use existing ones)
Create configurations (you can only use existing ones)
Change message records (table NAST) and additional message data (this data can only be determined via the message determination facility (Customizing))
Attach documents to the purchase order
Change foreign trade data
Change service data
Change or reexplode BOMs
A firewall prevents the manipulation of data that is not changeable in Purchasing according to the business logic of the purchase order (e.g. PO number, vendor, etc.).
PO items with an invoicing plan cannot be created or changed using the BAPIs
In this connection, please refer to current information in Note 197958.
To change addresses with numbers from Business Address Services (cantral address management), please use the function module BAPI_ADDRESSORG_CHANGE.
To change variant configurations, please use the function module BAPI_UI_CHANGE. More information is available in the BAPI Explorer under the Logistics General node.
In the case of changes that are to be made via the BAPI_PO_CHANGE, a firewall first checks whether the relevant fields are changeable. This approach follows that of the online transaction. Here it is not possible to change the vendor or the document type, for example.
Example
Example of changes made to a purchase order with:
1. Change in header data
2. Change in item
3. Change in delivery schedule
4. Change in account assignment
5. Change in conditions
6. Change in partners
Parameter: PURCHASEORDER 4500049596
Parameter: POHEADER
PMNTTRMS = 0002
PUR_GROUP = 002
Parameter: POHEADERX
PMNTTRMS = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
CONF_CTRL = 0001
Parameter: POITEMX
PO_ITEM = 00001
PO_ITEMX = X
CONF_CTRL = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
QUANTITY = 10.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELETE_IND = X
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELETE_IND = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
GL_ACCOUNT = 0000400020
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
PO_ITEMX = X
SERIAL_NOX = X
GL_ACCOUNT = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_TYPE = RA02
COND_VALUE = 2.110000000
CURRENCY = %
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 001
ITM_NUMBERX = X
COND_ST_NOX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further Information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
Parameters
PURCHASEORDER
POHEADER
POHEADERX
POADDRVENDOR
TESTRUN
MEMORY_UNCOMPLETE
MEMORY_COMPLETE
POEXPIMPHEADER
POEXPIMPHEADERX
VERSIONS
NO_MESSAGING
NO_MESSAGE_REQ
NO_AUTHORITY
NO_PRICE_FROM_PO
EXPHEADER
EXPPOEXPIMPHEADER
RETURN
POITEM
POITEMX
POADDRDELIVERY
POSCHEDULE
POSCHEDULEX
POACCOUNT
POACCOUNTPROFITSEGMENT
POACCOUNTX
POCONDHEADER
POCONDHEADERX
POCOND
POCONDX
POLIMITS
POCONTRACTLIMITS
POSERVICES
POSRVACCESSVALUES
POSERVICESTEXT
EXTENSIONIN
EXTENSIONOUT
POEXPIMPITEM
POEXPIMPITEMX
POTEXTHEADER
POTEXTITEM
ALLVERSIONS
POPARTNER
Exceptions
Function Group
2012
</b>
regards
prabhu
Message was edited by: Prabhu Peram

Gap of Time of R3 and PPDS planned orders

Hello Gurus,
I'm facing an issue regarding R/3 - PPDS planned orders.
The customer has the cenário that R3 and APO does not synchronize planned order on-line. R3 sends the orders on line however APO send it only in a determinated time. As a matter of fact, the issue happens when R3 planned orders are sent to APO. Anyhow, the order into R3 that should be delivered by 03/20/2010 for example, in APO, it is showed as 03/18/2010 or 03/19/2010 without apparently reason.
I realized that the R3 system server has a gap of 2 hour more in the system time if you compare with APO server, however I cannot understand the reason of this gap of days and I don't think that seems to be the reason.
Also, the capacity of the resource is not defined at the same time for a shift that is in R3.
Is there anyone that could help me about it?
Tks in advance.
Marcos.

Hi,
The time zone depends on the customization done - but one can change it to the desired option by setting the time zone in product view or requirements view as need be. One has the options of choosing:
Time zone of user
UTC Time zone
Location time zone
Any time zone the user prefers
so immaterial of the server location, one can change the settings according to the user requirements.
Regards
Vinod

SNP and PPDS planning horizons

Hai,
        I am reading through SNP and PP/DS planning horizons. I understand that SNP doesnot plan anything within SNP production horizon whereas PP/DS plans only within the PP/DS horizon.
Now, I get confused when trying to understand the following sentences:
1. If production horizon of SNP is smaller than the PP/DS horizon, the planning horizons of SNP and PP/DS overlap with each other. In this horizon, SNP determines the receipts with most cost-effective sources of supply and lot sizes and PP/DS plans the receipts in more detail.
2. If requirements within the SNP production horizon cannot be covered by PP/DS, then SNP plans the receipt outside the SNP production horizon(this corresponds to the logic in the PP/DS planning time fence in short term planning).
3. If the PP/DS horizon in the product master is set to be greater than SNP production horizon, this gives rise to an overlapping area in both SNP and PP/DS receipts are created.
Can anyone please help me undestand the above? An example or somedocumentation reference is appreciated.
Thank you.

Hi Visu,
Good question. You missed Planning Time Fence in the equation.
|--||--
>
1.       PTF             SNP            PPDS
You execute PPDS Heuristic (Product Heuristic) then requirements upto PPDS horizon will be covered by receipt elements (beyond Planning Time Fence). If you run SNP Heuristic then receipt elements will be created from SNP Horizon out in future deleting the receipt elements created by the previous PPDS run. But note that while PPDS planning is down to the second level SNP planning is minimum at a day level. If you have weekly buckets then all requirements for one week will be clubbed and single receipt element will get created. However you can consider SNP orders as fixed during PPDS Net Requirement Calculation through appropriate development.
|--||--
>
       PTF              PPDS           SNP
2. This is also not clear to me as I cannot build the scenario as described. The above diagram is the closest I could come up with. But in this case if you run SNP Heuristic and there are unmet requirements (sitting between PPDS and SNP horizon) then the receipt for that will be created only at the start of the SNP Horizon.
3. This is correct but already explained in 1.
Hope this clarifies or at least does not add to the confusion. BTW if you are interested then please read OSS Note 481906 - SNP - PP/DS integration (documentation).
Thanks,
Somnath

Planned order splitting during capacity planning

Hello,
anybody plese help me during the capacity planning in T.code.CM31 i want to split a planned order and want to assign alternative sequence. how can i do this and the capacity should be reschedule automatically to my requirement date. i am using backward scheduling.
plese suggest immediately
Thanks and reagards
Bhakta

Dear Bhakta
MRP does not perfom any Capacity Requirement Planning .While you are executing MRP with Lead Time Scheduling , MRP proposes Planned Order Dates based on the Routing Operation Timing not based on the Work Centre available Capacity because in SAP Std R/3 we did not have scope to check the finite scheduling and capacity requirement chek .MRP assume that Work Centre has infinite available capacity .
In MRP run , it will give you Detail scheduling of the Operation in Planned Order -Detail Scheduling tab and copied the routing , BOM as master data .When you convert that Planned order to Production order , it will copy the Routing details based on the Order Type denpendt Parameters -OPL8-Routing -Alternative sequnce and Automatic selection -3 option
Thats why we have Capacity Requirement Planning for Detail Capcity check and production order scheduling .
Note : Earlier to my first reply , please note that you have option in CM21 enter sequence number at order level which may applicable to you .CM21-Work Centre -exectute -Select the Order from order pool -Goto Order -Sequence number maintainence
This number( sequence number operation /order ) that can be assigned to production orders or planned orders at the level of the task list header and is therefore valid for all the operations in an order.
Hope this is clear .Revert if you nees farther help
Regards
JH
Edited by: Jiaul Haque on Jul 5, 2010 3:32 PM
Edited by: Jiaul Haque on Jul 5, 2010 4:01 PM

Bapi for sfg dependent dem,snp planned order qty, and ppds planned orde qty

Similar Messages

Maybe you are looking for