Diff between Detail scheduling & Apo Scheduling

Hi all,
Diff between Detail scheduling & Apo Scheduling
Thanks & Regds
Dhinakar

Hi Dhinakar,
i hope u are asking about difference Between Detailed scheduling of R/3 and APO scheduling.
R/3 Detailed Scheduling.
It is infinite scheduling - ie in which production orders and opeartions are scheduled without taking into account of existing workcenter load. Here over loading will be happened.
APO scheduling.
It is finite scheduling where by
existing capacity load is taken into account while scheduling. over load will not occur.
Here system will not schedule two production orders at same time. This one of the advantages of APO
Regards
Pradeep

Similar Messages

MRP based Detailed scheduling

HI All,
I was setting up MRP based Detailed scheduling
FIrst I had activated MRP based detailed scheduling in ERP
then I CIF materials, resources, planned orders & purchase req.
I had verified materials & resources in APO syatem.
Then I could see the orders CIFed to APO in product view.
then I was trying to view the orders in DS board and realise that there is no resource is linked to the orders and cannot view the orders in DS board and not able to do scheduling.
so what should be the solution? Can anybody help me out?

Binil,
From your brief description, I belive you have overlooked CIFing over some Master data, either PDS or PPM.
You must create a Production Version in R/3 first. This contains the relationship between material and resource (which is contained in the routing).
For an example of how to set up PP and DS, there re some nice configuration guides in SAP SCM best practices. You will need
Connectivity
http://help.sap.com/bp_scmv250/BBLibrary/HTML/B02_EN_DE.htm
Replication
http://help.sap.com/bp_scmv250/BBLibrary/HTML/B05_EN_DE.htm
Production Planning
http://help.sap.com/bp_scmv250/BBLibrary/HTML/S16_EN_DE.htm
Detailed Scheduling
http://help.sap.com/bp_scmv250/BBLibrary/HTML/S18_EN_DE.htm
Best Regards,
DB49

Link between Delivery schedule line counter from PO and the material docume

Dear Gurus,
I have one PO with single line item having delivery schedule -
Material 1 -
delivery schedule 01.01.2009     2000
                                                     01.03.2009    5000
I have received quantity against this Po
I want to know where I can find the link between Delivery schedule line counter from PO and the material document
Best regards
Sar

There is no link from the MAterial document line item (Table Mseg) to the PO Schedule Line (EKET).
If this is for Evaluating an on time delivery or GR, you may consider the following approach.
PO details Po Date QTY
Sch1   01Jun2009   200
SCH2 08Jun2009   100
GR Details
GR1   01Jun2009   180
GR2   07Jun2009   110
GR3 09Jun2009      10
Calculate a *** total qty for the PO Line.
PO details Po Date CUMUL QTY
Sch1   01Jun2009   200
SCH2 08Jun2009   300
Calculate a *** total qty for the ontime GR.
PO details Po Date CUMUL PO QTY CUMUL GR on time
Sch1   01Jun2009   200                180
SCH2 08Jun2009   300                 290 (180+110) the 3rd GR was too late
Evaluate the PO SChedule Lines as follows:
Po SCL qty + CUMUL GR QTY - CUMUL PO QTY = ADJ GR ON Time Qty
SCH1 01Jun2009
200 + 180 - 200 = 180 on time for 01Jun2009 date ( 90% fill rate)
SCH2 08Jun2009
100 + 290 - 300 = 90 on time for 08Jun2009 date (90 % fill rate) the first 20 of the GR on 07Jun2009 went to fill the late, early date.
Best of luck !
SCH2 100 +290 - 300 = 90 on time for 07Jun2009 date

What r the diff types of schedule line categoriesr there ? purposes of its?

what r the diff types of schedule line categoriesr there ? purposes of its?

Deva, you are asking A LOT of basic SD questions which you can find answers to in standard SAP documentation available on line.
Please read that stuff first, and keep your questions here to more specific configuration / transaction details
Thanks in advance

Difference between Periodic scheduling & deadline Monitoring.

Hi Gurus,
i want to know the difference between Periodic scheduling & deadline Monitoring.
its gud if u explained with short example.
Thanks in Advance..
regards,
Amol.

Hello,
If you enter the start date or initial counter reading in the scheduling parameters, then you can start the automatic deadline monitoring directly for the maintenance plan (see Scheduling a Maintenance Plan automatically).
If you do not enter the start date or initial counter reading in the scheduling parameters, then you must start the scheduling for the maintenance plan manually before you can start the automatic deadline monitoring (see First-Time Scheduling).
For More Details about Schedulin you can refer below Link [http://help.sap.com/saphelp_nw04/helpdata/en/3c/abb350413911d1893d0000e8323c4f/content.htm]
Reagrds,
Rakesh
Edited by: RAKESH ASHOK MANE on Aug 24, 2010 12:29 PM

Link between the Schedule Lines and the GR document

Hi
I would like to find the link between the Schedule Lines (of Scheduling Agreement) and the GR document. i.e. which GR has been made against which Schedule Line. I have checked the tables EKET, EKBE, MSEG but there is no link with the Schedule Line, I found the link only with the item number there.
Thanks
Prashanth

Hi
At the time of posting the GR for a SA you will be not posting this with reference to the Schedule line of the SA item. So system will always update the GR document against the SA item and update qty on the schedule line.
May be this is the reason we donot have any direct relation ship to material document and Scheclue line
Thanks & Regards
Kishore

Link between delivery schedules in purchase order and GR document

Dear all,
Can you provide link between Delivery schedules in po and gr document. for which schedule gr is done etc.
With Regards,
prasadbabu

i want fields mblnr and eindt in one table.
With Regards,
PrasadBabu.

Diff between Planning in BPS and Planning in APO

Hello..
Can any one give me some good insight in to the difference between planning in APO and plannning BW BPS.. In what way is it diff?
thankyou..
kishore karnati

Hi Kishore,
Not sure about APO but some of the distinct features of BPS planning are:
Loose integration with the transactional data flow
Fast and simple adaptation to current and future organizational changes
Free and unrestricted definition of integrated planning scenarios
One homogeneous planning environment for the flexible design of various planning steps
One central data warehouse as basis for all information needed in the decision process
More simulative planning processes
Maybe an APO expert could comment on the other side
Hope it helps...

DIFFERENCES between BASIC SCHEDULING and LEAD-TIME SCHEDULING.

Hello SAP Gurus,
Kindly let me know the differences between BASIC SCHEDULING and LEAD-TIME SCHEDULING.
Looking for your early feedback.
Warm regards,
Kaushik.

Hi,
Basic scheduling :
1.Basic dates are calculated.
2.Exact to day.
3.No cap reqmts are generated.
4.uses the inhouse production time from material master.
5.carried out automatically during planning run.
In basic date calculation ( order start date/ order finish date ) the system always
calculates backward scheduling.
1. From the reqmts date the system subtracts the GR processing time to
calculate the order fininsh date.
2. From the order finish date the system subtracts the inhouse production time to calculate the order start date.
3. From the order start date the system subtracts the opening period given in scheduling margin key to calculate the order opening date.
Lead time scheduling :
1.Exact to second
2.ie production start date /time and finish date and time are calculated.
3. cap reqmts are generated.
4. uses times from routing.
5. carried out only if the scheduling mode in MD02 screen is kept with indicator 2.
From the order finish date the system subtracts the float after production to calculate the production finish date.
From the production finish date the individual operations in the routing are scheduled backwards to calculate production start date.
From the production start date the system subtracts the float before production
to calculate order start date.
Regards,
nandha

Detail scheduling

Hi All,
After runing the MPS system creates the Plan orders as per set MRP data but the querry is if there are more than 1 orders, Why scheduling of each orders is on same date & time for the same production version?
What type of scheduling data required to do detailed scheduling like scheduling of the next order should be after the comletion of previous order.
Regards,
Dhaval

Hi Dhaval,
During the MRP/MPS run system will not taken the capacity requirement in Account.It assumes capacity in infinite.
That is why R/3 is required, capacity leveling after MRP/MPS.
In capacity leveling u can reschedule the planned order as u need. (CM25) .
Pradeep

Diff between ECC5.0 and ECC6.0

Hi,
This is Ramakrishna,can any one give proper explanation diff between ECC5.0 and ECC6.0
Regards
Ramakrishna

Hi,
Refer following link;
[SAP ERP Solution Browser|http://solutionbrowser.erp.sap.fmpmedia.com/]
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
- Goods receipt
- Goods issue
- Transfer posting
- Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
- To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
- Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
- Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
- Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
- 107: Goods receipt to valuated goods receipt blocked stock
- 109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location

Issue in CIF data between ECC to APO

Hi Experts,
We have ECC and APO system in our landscape. we have configured CIF and transferred data between ECC and APO however after ECC system refresh CIF configuration is not working. we verified and reconfigured the CIF configuration but still no luck.
strange thing is, while sending the data for e.g vendor from ECC to APO, there is no error reported. It displays successful in both qRFC trace files but the transferred data is nt reflecting in APO system.
There is no system run time error, no errors in system log (SM21), no logs in SLG1 application log, no erros in qRFC trace files.
we have enabled RFC user trace but can't conclude the issue. could you please anyone let me know where we can check the error log or how to resolve this?
Outbund Queue logs from ECC:
QTYPE :OUTBOUND/S
DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:44:56 300             20.03.2015 17:44:56 N          N
        0A1A01720F70550C0F4019E7                                       SENDING
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                      QTYPE :OUTBOUND/S
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:44:57 00:00:01 300          20.03.2015 17:44:56 N       N
        0A1A01720F70550C0F4019E7                                       CONFIRMD
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                      QTYPE :OUTBOUND/S
DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:44:57 300             20.03.2015 17:44:56 N          N
        0A1A01720F70550C0F4019E8                                       SENDING
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                      QTYPE :OUTBOUND/S
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:44:57 00:00:00 300          20.03.2015 17:44:56 N       N
        0A1A01720F70550C0F4019E8                                       CONFIRMD
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Inbound Queue trace log from APO:
QTYPE :INBOUND
DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 300                20.03.2015 17:44:56 N          N
        0A1A01720F70550C0F4019E7                                       SENDED
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 17:39:48 300             20.03.2015 17:44:56 N       N
        0A1A01720F70550C0F4019E7                                       FINISH
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                       QTYPE :INBOUND
DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 300                20.03.2015 17:44:56 N          N
        0A1A01720F70550C0F4019E8                                       SENDED
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 17:39:48 300             20.03.2015 17:44:56 N       N
        0A1A01720F70550C0F4019E8                                       FINISH
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      RUNNING
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      FINISH
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      CONFIRMD
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      RUNNING
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      FINISH
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      CONFIRMD
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
Thanks and regards,
Pradeep

Hello Pardeep,
Please check the setting of SMQS and SMQR for CF and client registration
these entries, the field 'TYPE' is set to 'R'.
QIN scheduler may be available for every client if you are working in this client with registered inbound queues.
Choose Edit->Activate scheduler from the menu (available in both SMQR and SMQS)
During processing in dialog work processes, the system uses a parallel RFC to restart the registered inbound queues. For this, you can use transaction RZ12 to specify a group of application servers and dialog work processes that are allowed to use a QIN scheduler. You must use transaction SMQR to assign the group name to the relevant QIN scheduler.
Different parameters in SMQR are explained in note 1579728. The explanation for SMQS is similar
Also try the report RSQIWKEX
Best Regards,
R.Brahmankar

Diff between programme BBP_GET_STATUS_2 & CLEAN_REQREQ_UP in SRM7.0

Hi Experts ,
We have ECC6.04 with SRM 7.0 with Classic Scenarion
I am confused over exactly what BBP_GET_STATUS_2 do in SRM ?
I believe CLEAN_REQREQ_UP update the SC with follow on document i..e Classic PO....
and BBP_GET_STATUS_2 update the entries in BBP_DOCUMENT_TAB..but not getting exactly what is does..since if we change qty in Classic Po ..it automatically updates automatically in SC follow on document...if we Craete GR in ECC it updates automatically in SC follow on document...
Can anyone please suggest me exactly what BBP_GET_STATUS_2 do in SRM ( what is exact diff between both )?
Thanks
NAP

Hello,
Report : BBP_GET_STATUS_2
Function : This reports updates the requirement coverage requests (Shopping carts) to ensure that information on the status of backedn purchase requisitions, purchase orders, and reservations is up-to-date.
You should schedule this report to run daily in the SRM server system.
Report : CLEAN_REQREQ_UP
Function : Interval for update check.
Updating of documents (purchase requisitions, purchase orders, reservations) is executed asynchronously in the backend system. You can only process the requirement coverage request in the SRM server system further after the update has been carried out. At the interval defined by you in Customizing, the system checks whether the documents have been updated and thus if you can further process the requirement coverage request.You should schedule this report periodically.
Hope this helps.
Best Regards,
Rahul

Diff between Precalculated Value set and Precalculated web template

Hi Friends
Can any one tell the Diff between Precalculated Value set and Precalculated web template
Where we will use these
Thanks

Hi,
The Reporting Agent is a tool used to schedule reporting functions in the background.
The following functions are available:
●      Evaluating exceptions
●      Printing queries
●      Pre-calculating Web templates
●      Pre-calculating characteristic variables of type pre-calculated value sets
●      Pre-calculation of queries for Crystal reports
go through,
pre-calculated value sets
[http://help.sap.com/saphelp_nw04s/helpdata/en/28/734d3caa70ea6fe10000000a114084/frameset.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/84/00783b3af21f5ee10000000a11402f/content.htm]
Pre calculating Web template:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9e/9f653ade969f4de10000000a114084/frameset.htm
Basically when you have a Precalculated Template, the system first run a report (which has been scheduled) and read the data from there when you run your template. This can imrpove the performance respect to online read data.
[http://help.sap.com/saphelp_nw04s/helpdata/en/6e/b5663a5fb46752e10000000a11402f/frameset.htm]
[Pre calculated web template;
Hope this helps...

What is the diff between general gl a/c, control a/c, reconciliation a/c,

Dear All
what is the diff between general gl a/c, control a/c, reconciliation a/c & offsetting a/c.

Hi,
Normal GL Account is the account where the accounting entries are posted. GL Accounts will be broadly of two categories like Balance Sheet Accounts (Assets & Liabilities) and Profit & Loss Accounts (Income and Expenses).
Reconciliation Accounts are used where a subsidiary ledger is maintained. For example for Customers and Vendors details are maintained in separate ledgers but the control totals are posted in the Reconciliation Account which is part of GL Accounts. Similarly reconciliation accounts are maintained for Assets and Materials also. Further, in case of Customer and Vendor accounts the number of line items will be very high, hence only the totals are updated in GL and line items will be individual ledgers. Basically reconciliation account and control account are similar.
Offsetting Account: In Financial Accounting for every debit there should be a corresponding credit. So when ever any entry posted it will normally hit two GL Accounts. When we look at one line item, we will be interested where the other side of the entry is posted. This entry is the offsetting entry.
If you find this usel, please assign points.
Thanks
Murali.

Diff between Detail scheduling & Apo Scheduling

Similar Messages

Maybe you are looking for