Cross-Docking, Deliveries and availability check

Friends & Gurus,
From what I read, Cross Docking (ECC 6.0) works with deliveries. I can link an inbound to an outbound delivery so as soon as the goods are received they head straight to the outbound delivery.
If I plan to use X-Docking for stockouts, how can I link the deliveries if the outbound cannot be created because of availabity check (no stock on hand).
Question: Should I change the availability check of the outbound deliveries so I can create them without stock on hand in order to use X-Docking functionality?
Thanks stranger!

Hi
If you are talking about blocked stock you can remove the check for blocked stock in OPJJ transaction. this will make availability check will not consider blocked delivery
If useful reward points
Regards
Ranga

Similar Messages

MRP and Availability check clarification

while browsing the forum, many experts here mentioned in old threads that MRP and availability check are two different (independent) concepts. I am really confused on this one. let me put my understanding here and plz experts help me if I am wrong with a figurative explanation, so that will be easy for understanding.
Assume this is the scenario as of today.
Plant stock for material x u2013 100
Reservations for material x u2013 70
Incoming receipts for material x u2013 50
So net stock = 100 + 50 -70 = 80
sales order arrived for material x u2013 100 and availability check is done. Results of availability check says 80 can be confirmed and 20 can be confirmed on later date.Transfer of requirement for quantity 20 is done to MRP. Mrp runs and creates planned order for 20.
In the availability check config ovz9 if I say donu2019t consider reservations, then when availability check is done for 100 quantities..system will confirm 100 because available stock according to system will be 100+50 = 150. So transfer or requirements are not sent to mrp.
So isnu2019t mrp run directly dependent on availability check?

925,
sales order arrived for material x u2013 100 and availability check is done. Results of availability check says 80 can be confirmed and 20 can be confirmed on later date. Transfer of requirement for quantity 20 is done to MRP
No. 100 pcs requirements are passed to MRP.
In the availability check config ovz9 if I say donu2019t consider reservations, then when availability check is done for 100 quantities..system will confirm 100 because available stock according to system will be 100+50 = 150. So transfer or requirements are not sent to MRP.
No, 100 pieces requirement are passed to MRP.
This behavior depends upon how your 'transfer of requirements' is configured, which is an SD setting. Normally, unless the fix date qty field is set in the sales order, the entire 100 pc requirement is passed to MRP in all cases. The assumption is that you have accepted the sales order and will 'some day' need to issue and sell the parts. You need to begin planning for this event now.
When MRP subsequently runs, it will net out the supply elements (stock and inbound reservations) and will from this calculation determine how much needs to be built. It then proposes a solution (planned order or purchase req).
ATP check seldom has much impact on MRP. You are correct in realizing that the ATP check must be consistent with MRP and with your chosen MRP strategies, in order to provide an end-to-end business process that is logical and meets all business requirements. However, in SAP these two functions are separate.
Best Regards,
DB49

Credit block and Availability Check

Hi,
As per standard behavior when there is credit block in sales order, system does not confirm the quantities when the sales order is saved even though receipt elements are available during availability check.
Is there any way to confirm the quantities even though sales order is into credit block.
Regards,
RS

Hello,
In requirement like yours we can Confirm the Quantities & insert a Delivery Block. To do this follow as below:
IMG - Sales and Distribution - Basic Functions - Availability Check and Transfer of Requirements - Transfer of Requirements - Block Quantity Confirmation In Delivery Blocks - Deliveries: Blocking Reasons/Criteria -
Here for Delivery Block 01 - Credit LImit - There will be a tick mark in Confirmation block (Conf) Box. Remove this tick mark & then system will Confirm the Stock inspite of Credit Block.
These block are defined here:
IMG - Sales and Distribution - Basic Functions - Availability Check and Transfer of Requirements - Transfer of Requirements - Block Quantity Confirmation In Delivery Blocks - Reasons for and Scope of Deliv.Blocks: Transfer of Req.Block
Hope this helps,
Thanks,
Jignesh Mehta

Blocked Goods and availability Check

Hi,
I have a scenario where certain quantity of a material say "a" was blocked.But after certain time due to increased demand the client asked to make the material "a" available.So how does the availability check will work now..
Thanks

Simple, you need to have stock for the material. You schedule line cat relevant for Availability Check in sales order will take care of it.
If you have existing sales order for the material then use TCode V_R2 and V_V2 for running the availability check for unconfirmed items of the sales orders.
Or you can use V_V1 used to create confirmed backorder.
Regards
JP

Third Party Drop ship and availability check against Product Allocations.

Dear All -
We are facing a situation where we need to create a third party drop ship Sales Order with an item category which still reaches out to APO and confirms against the product allocation quantities. This is not supported by standard SAP.
Has anyone come across such a requirement and how has it been handled. I would really appreciate any suggestions.
Regards
Mandar

Vladimir,
I want the drop ship in which when you create SO, before selecting the vendor, system should perform availability check for plants. If material is not available in the plants ( nearest plant) then system should select the vendor who will ship the material to customer directly.
_pat

MRP planning and Availability check

Dear Friends ,
We are updating Availablity check in the MRP view for all materials in materials master , While running MRP system is considering ATP check as per SPRO settings defined for Availablity check group .
Weare not conclude what is the relation for MRP run and availablity check , or any seperate SPRO settings available for MRP on availablity.
If we not assigned the Availablity check in MRP view what will happen if during MRP run ?
thanks & regards
Suresh Babu.S

Suresh,
MRP does not look at what you have configured for Availability check. These two are independent from each other.
As given in Help,
In the planning run, the system carries out the following partial processes:
1. The system checks the planning file entries. Here, the system checks to see whether a material has been changed in some way relevant to MRP and should therefore be included in the planning run (see Checking the Planning File Entries).
2. The system carries out a net requirements calculation for every material. Here, the system checks to see whether the requirement quantity is covered by available warehouse stock and fixed receipts from Purchasing or production. If the requirement quantity is not covered, the system creates a procurement proposal (see Net Requirements Calculation).
3. Then the system carries out the lot-sizing calculation. Here, the system takes the lot-sizing procedure and, if necessary, the rounding up or down values into account (see Lot-Sizing Calculation).
The system carries out scheduling to calculate the start and finish dates of the procurement proposals (see Scheduling).
4. The system determines the type of procurement proposals. Depending on the settings, the system creates either planned orders, purchase requisitions or schedule lines for a material (see Determining the Procurement Proposal). If you have maintained the necessary specifications for procurement quota arrangements, the system determines the source of supply which it assigns to the procurement proposal (see Quota Arrangements).
5. The system recognizes critical situations which the planner has to processes manually in the planning results. For this purpose, the system creates exception messages and carries out a rescheduling check (see Creating Exception Messages and Rescheduling Check).
Availability check is not a planning process, it is basically a CHECK, based on the Scope of check derived for that Particular transaction, system check the availability of a material and it can confirm or propose the possible availability date.
In short if a material is defined with Check Group "KP", but with MRP type PD, still MRP would creates procurement proposals if the demand is more than the stock+recipets.
Regards,
Prasobh

Budget by periods and availability check (AVC)?

HI ,
Can we have Budget by periods and with availability check (AVC)?
for ex: for
WBS element 1 for January -1000 USD for Feb 5000 USD. And so on...Total yearly budget is 15000USD.
And
WBS element2: January -1500 USD, Feb 2500 USD and so on ...total yearly budget is 25000USD.
If the budget Exceeds for the particular WBS element for the particular period then it should give message (error/warning/).
Can we implement this in Project system?
Thanks for your time

To give budget by period (Month ) is not possible in PS. Budget is annual / overall in PS. you requirement can be achieved by monthly you provide budget to WBS in the form of supplement.
This way indirectly you can achieve the same.
Please refer this post.
Project Budget by Month
Regards
Nitin
Edited by: Nitin Patoliya on Feb 3, 2009 8:40 AM

Error in va01 for transfer of reeqirement and availability check

hi every one when i have done TOR and availabilty check configuration it is not reflecting in va01 can any one help out with configuration step by step

HI
Kindly check the Google with Same text so you can find out so many documents which is related to Availability Check & TOR
Coming to your Question , try to check the Schedule line Category (VOV6) , you need to TICK the Field *"Availability" * Requirement/Assembly"*
and also kindly check the Below
link [Availability Check (ATP) and Transfer of Requirement (TOR)|http://wiki.sdn.sap.com/wiki/display/ERPLO/AvailabilityCheck(ATP)andTransferofRequirement+(TOR)]
[Available to Promise (ATP)|http://wiki.sdn.sap.com/wiki/display/ERPLO/AvailabletoPromise+(ATP)]
Regards,
Prasanna

Schedule Line Category and Availability checks

Hi Folks,
A generic question.
Wanted to know, how would availability check results influenced if only Item category and MRP type are maintained and not the scheduled line categories.
Was trying to figure a strange Availability check behavior of non-confirmation for one item category and confirmation for another- item x location being same. The ATP checks settings are maintained and called from GATP. (not R/3 and R/3 customization is not imported too).
Regards

closing

Schedule line and availibility check

Hello,
I have three questions ;
Q1) my schedule line category is set to " no avalibility check".
Q1A) How does the system confirms the stock in sales order or in delivery if schedule line category is set to "no avalilibity check"
Q1B) does the sales order and delivery appear in MD04 is schedule line category is set to "no availbility check".
Q2)my schedule line category is set to " no materials planing ?
Q2A) How does the system confirms the stock in sales order or in delivery if schedule line category is set to "no materials planning"
Q2B)does the sales order and delivery appear in MD04 is schedule line category is set to "no materials planning"
Q3) what is the relationship between MD04 and MRP run. Does all the sales orders or deliveries appear in MD04 after MRP run ?
request pls answer pointwise for clarity
regards
sachin

hi Sonu,
Q/3 ) relationship between MRP run & MD04
>The function of MRP is to plan the requirement of a header material as well as for the dependent requirements.This is done with the transaction code MD02.All the requirements are pulled up and planned.the outcome of the run will be a report which will show the details of the planning like
>Materials planned
>Materials with new exceptions
.MRP run is therefore static.
>MD04 shows you the stock requirement list of the material.after you run the MRP for a particular material this screen will show you the requirement for header materials,
dependent requirement,available stock,the reservations made.if the stock is less u can either generate PR for externally procured or create prodn order for internal mfred.
this is dynamic i.e whenever u run this t code u get the latest update on the status of that material.
u can't see deliveries in MDO4 only reservations
SO are not seen directly but as a customer requirement and when u run MRP they are changed to planned order.this planned order can be seen in MD04 from where u can either create PR or production order
Q/2B
"no planning " is used for those items for which u don't want to run MRP.certain materials are such that the controller can manage w/o running MRP i.e the SO comes and the product is either delivered or produced w/o running MRP.
hope this helps,
regards.
Edited by: vikas koul on Jun 26, 2008 1:27 PM

Complete Deliv and Mixed Item cat and Availability Check

Hi Gurus,
Not sure if this is problem is new, I have searched with no clues.
A SO has 2 item categories. ZTAN, ZTAS. ZTAN is stock item, ZTAS is back to back item where a PO will be created. Same material. There is a GR processing time of 10 days.
SO created on 12.05.2014.
Item 1: MatA     First Date: 15.05.2014     Item Cat: ZTAN Qty: 500     Confirmed Date = 15.05.2014 (Stock Available)
Item 2: MatA     First Date: 15.05.2014     Item Cat: ZTAS Qty: 1000     Confirmed Date = 29.05.2014 (Today + 10 GR Process)
Then tick Complete Deliv. Indicator in SO overview screen.
Item 1: MatA     First Date: 15.05.2014     Item Cat: ZTAN Qty: 500     Confirmed Date = 29.05.2014
Item 2: MatA     First Date: 15.05.2014     Item Cat: ZTAS Qty: 1000     Confirmed Date = 29.05.2014
Save SO.
PO 1st AB line for SO item 2: Confirmed Date = 15.07.2014 results in Both SO item confirmed date = 15.07.2014
PO 2nd AB line for SO item 2: Confirmed Date = 15.06.2014 results in Both SO Item confirmed date = 15.07.2014.
You see the problem is after 2nd AB, confirmed date in SO does not change to earlier confirmed date. And even if we run the standard back order processing V_RA or V_V2, system still does not schedule earlier.
Any solution?

Then tick Complete Deliv. Indicator in SO overview screen.
Item 1: MatA     First Date: 15.05.2014     Item Cat: ZTAN Qty: 500     Confirmed Date = 29.05.2014
Item 2: MatA First Date: 15.05.2014 Item Cat: ZTAS Qty: 1000 Confirmed Date = 29.05.2014
Save SO.
PO 1st AB line for SO item 2: Confirmed Date = 15.07.2014 results in Both SO item confirmed date = 15.07.2014
PO 2nd AB line for SO item 2: Confirmed Date = 15.06.2014 results in Both SO Item confirmed date = 15.07.2014.
When you say system has confirmed in the first instance (29.05.2014), I am not sure where system is showing 15-06-2014 & 15-07-2014.
G. Lakshmipathi

TOR and Availability Check,

Dear Friends,
I have two questions:
1.What should be the Ideal requirement to be used ...is this
    011-Delivery requirement
    041-Order/delivery requirement
2.The MRP type i am using is Manual reorder point(V1).
During "Determination Of Requirement Types Using Transaction" Iam not able to create new entry with V1...ie Item category and the MRP type are in display mode....
TAN + V1 - 11(Delivery requirement)
Thanks
Sasi

Dear Friends,
I have two questions:
1.What should be the Ideal requirement to be used ...is this
    011-Delivery requirement
    041-Order/delivery requirement
2.The MRP type i am using is Manual reorder point(V1).
During "Determination Of Requirement Types Using Transaction" Iam not able to create new entry with V1...ie Item category and the MRP type are in display mode....
TAN + V1 - 11(Delivery requirement)
Thanks
Sasi

TCD- Unable to send Cross docking documents to EWM

Hi Experts,
I am working on TCD scenario with ref. to a Sales Order without Storage Control. I am able to get pair of documents created in ECC (Inbound Delivery and Outbound Delivery). But these documents not able to get distributed to EWM. SMQ2 show the following error.
Could not determine a supply chain unit for ERP warehouse number KS1
Message no./SCWM/ERPINTEGRATION018
Diagnosis
The delivery document from ERP contains a plant for which Extended Warehouse Management (EWM) cannot
find a corresponding supply chain unit.
System Response
EWM does not create an EWM delivery document.
Procedure
Define the missing supply chain unit. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management -> Master Data -> /SCMB/SCUMAIN - Maintain Supply Chain Unit.
KS1 is my cross docking WH and this WH has SCU and maintained in above path and also has hierarchy maintained. As mentioned in error, Plant in delivery document is Plant1 (Supplying plant) and WH is Cross Docking WH.
Supplying plant has SCU maintained in EWM, otherwise my initial Outbound Delivery could not have got processed in EWM.
Please suggest what setting that I am missing.
Appreciate your help in this regard.
Thanks
Mahesh.

Hi Mahesh,
Check the attributes for supply chain unit.
Check Availability group table assignment table (under GR assignment in customization )
Regards
Suraj

Cross docking in WM

HI,
can anyone explain about the usage of cross docking functionality and how to use it.
how to link an inbound docume

Hi Susil,
Cross-docking implies moving materials directly from the incoming to the outgoing physical areas of the warehouse. To process these materials without first putting them into storage, the warehouse must be aware of what deliveries are coming in and which deliveries are going out.
Inbound delivery helps in planning of incoming Materials in the Warehouse hence can make use of effective implementation of Cross Docking.
Cross docking can be monitored using Cross Docking Monitor. Details of the Cross docking monitor are well explained in the link below
http://help.sap.com/SCENARIOS_BUS2004/helpdata/EN/fc/efc43f82ab6d3fe10000000a114084/content.htm
Regards,
Ramakrishna

TOR and availability

Hi all,
which will happen first TOR and availability check

dear lsayah
once you enter the qty in the order system will send the requirement to procurement TOR ( transfer of requirement ) then availability check will happen
that perticular material for perticular qty on perticular date will available or not
the details notes on TOR and Availability check
TOR AND AVAILANBILITY CHECK
To confirm the quantities for a particular line item in the sales order on particular day system carried out transfer of requirements (TOR) & AVAILABILITY check, so has to confirm the quantity on particular day as system should know what are there requirement of the sale order and delivery with MRP then system carries out availability check function, to confirm the quantity on particular day. Depending upon the IMG setting system carries out availability check function based on 3 methods:
A) Availability Check with ATP logic or against planning:
In ATP logic systems ATP Qty while carrying out availability check function for
Particular line item (ATP qty=warehouse stock +planned receipts planned issues)
Planned Receipts: EX: - purchase requisitions, purchase orders, stock in transfer stock at inspection etc.
Planned Issues: - EX: - open sales order & open delivers
B) Availability check against product allocation:
Availability check can be carried out against product allocations in which system automatically restrict the user to confirm the quantity beyond reserved quantities per particular customer. EX:- Availability qty =100, existing orders=10,then system automatically distributes to items evenly to the sales order.
C) Rule based Availability check:
Rule based availability check can be carried out based on the business transaction.
EX: - For normal sales order system has to carry out availability check for special sales order ex: - cash sales and rush order systems need not to be carry out availability check,
In rule based availability check system in which system carried out Global availability to promise in all plants. In this check system transfers the requirements to APO system where GATP takes place and the result of the availability check transferred to R/3 system. This process takes place with the transaction code CIF(central inter face) inR/3.After carrying out availability check function system proposes(by using ATP logic) default values of ATP check result to the user in a dialog box, in which system gives the choice to the user to take the decision in contest of insufficient stock.
a) One time delivery:
If the user chooses one time delivery and the order Quantity is 100 units system confirms 50 units then systems automatically confirms as a zero. If the user saves the document with the zero confirm qty then system   trace the sales order as aback order (V_RA), which can be confirmed later by RESCHEDULLING (V_V2).
b) Complete Delivery:
If order Qty=100, Availability stock = 50, system says that remaining can be given after one week. Then if the user selects this option then system push up existing confirmed qty to after one week and the total qty can be confirmed after one week only.
c) Delivery Proposal:
If order qty=100, system confirms 50, and remaining 50 can be confirmed after one week. If the user chooses this option then system confirms 50 Qty today allows the user to delivery 50 quantities today remaining 50 can be delivered after one week.
CONFIGURATION SETTINGS FOR TOR:
Define Requirement Class:
Path: Img  S&D  Basic functions  Availability Check & Transfer of requirements  Transfer of requirements    Define Requirement classes
Requirement classes control MRP, Requirement consumption, strategy, relevance for planned. It specifics whether the availability check & TOR to be Called out for transactions. Ex: Sales Order
It determines whether requirements relevant for MRP or not, the allocation indicator from the sales view which controls the settlement of customers requirements with planned independent requirements. It determines the item b to be settled as an availability heck. Assignment, the settlement profiles the results analysis key. The TOR and Availability check functions are globally controlled using the requirement class for all the Sales documents. The values from the Requirements class are transferred to scheduled the of the sales documents class are transferred to scheduled the of the sales document default values and can be over written there.
Define Requirements Classes:
Requirement class defines whether the system has to carry out availability check based on the STP Qty. Ex:
Define Requirement Types:
Here we define requirement type, Ex: and Assign to Requirement class that we defined in the promote step.
Determination of Requirement types using Transaction:
Requirement type is going to be determined for sales document by following a search strategy. .
First System checks strategy group in MRP3 view if it trend requirement type then system takes from it, otherwise.
It will go to MRP group in MRP1 view, otherwise
It will check to Material type, otherwise
It will go to item Category + MRP type, otherwise
It will go to Item category only, otherwise
Finally system determines the transaction b not relevant for TOR & Availability check.
Choose Item category TAN+MRP type PD=Requirement type =0
Define Procedure for each schedule the category:
Here we define respective schedule the category of the sales documents, whether an availability check and TOR should be carried out. This setting is relevant for sales documents only. It is fine tuning of availability check for sales documents TOR & Availability check function    can be activated at sales order level those are proposed in to schedule line category level. If u wants to deactivate TOR availability check function at schedule the category level and want to deactivate at requirement class level it b impossible.
Ex: If u wants to check availability w/o transferring the requirement we can use it.
Choose schedule line category CP & Activate Availability check, requirement & Product Allocation
Block Quantity confirmation in delivery Blocks:-
When we transfer requirements to MRP then confirmed quantities is also reserved for confirmed sales documents, if transaction is blocked for delivery the reserved quantities are also blocked so that the conformed quantities cannot be used by any other purpose. So has to avoid this situation we can block the transfer of requirements(TOR) for delivery blocks, in this case requirements transferred to MRP but will not be reserved, that will be cleared once we save the documents then system shows confirmed qty as zero.
When we remove the delivery block then system automatically carries out availability check & confirms the qty.
A) Deliveries: Blocking region for sales Area:
     Here we define blocking regions for TOR ex:-credit limits
B) Reasons for scope of delivery blocks: TOR. Block:
Ex: - 01 credit limits-check confirmation block.
Maintain Requirements for TOR:-
Here we can define our own requirement with the help of ABAPer for TOR
Ex: - a) 102- prevent reservation in the event of credit block
       b) 102-purchase requisitions.
System doesnt create purchase requisitions for sales order line items if it has a credit limit.
Availability check:
Configuration setting:-
Availability check with ATP logic or against planning:-
Define checking group:
Checking group define what kind of requirement record system use to create when sales order & deliveries are processed for this material. We can create 2 kinds of requirements records
Individual requirement records: that means system creates requirement record for each S&D document.
Summarized requirement Records: That means system creates requirement records under certain condition in the material master record. There are 2 type of summarized requirement record:
Summarized requirement records for each day.
Summarized requirement records for each week
Define checking Action;
Here we define 01- daily requirement      -B                                    02- Individual requirements -A
Where b-total record per day
     A-single record per day
B) Define material Block for other users:
When 2 users tries to confirm the quantities for the sales order for same material at a time system will be confused to confirm the quantities both sales orders. So has to avoid this kind of situation we can block the materials from confirming the quantities for 2 users at a check, check block
C) Define checking group default values:
Checking group is going to be determined depending upon the material type & plant.
-Go to new entries, specify material type, ex;-FERT
& plant = checking group of availability check: 02
D) Carry out for Availability check:
Here we define checking rule for the Availability check & allocate them to the checking group. The checking rules specify the scope of the availability check. For a respective transaction, means which planned receipts & planned issues systems has to taken into consideration and also it determines whether system has to take RLT into consideration.
Action:
*Select checking group of availability check-02, checking rule=01
*Go to details icon, & check which planned receipts & planned issues system has taken into consideration for availability check
*save it, exit.
E) Define procedure by Requirement class:
Here we define requirement class whether on availability check & TOR should be carried out the setting that we carries out at requirement class level they are at global level. There settings automatically copied into define from of requirement class and vice versa.
Action:
*Choose requirement class: 041 & check availability check & TOR (requirement)
F) Define procedure for each schedule line category:
Here we carry out fine tuning setting for availability check at schedule line category level. Here we define whether system has to carry out Availability check for particular transaction.
Ex:- if we want to implement a availability check w/o TOR for a particular transaction. According to settings at requirement class level TOR & availability check function activate & those setting will be copied into the schedule time category by default, so that at schedule line category level we deactivated TOR
G) Determine procedure for each Delivery Item category:
Here we switch on or switch off availability check functions of a delivery item category
*choose item category TAN. & specify the appropriate value.
H) Checking group for updating back orders:
Here we assign checking group to a plant that rule specifies for individual application, according to which the availability check is carried out;
I) Define Default settings:
Here we define the result of the availability check.
*Choose your sales Area, & check fixed dates& Qty options & specify D or E
Where: D- Dialog box in the case of shortages (one time delivery)
E- Dialog box in the shortages (delivery proposal).
rewards if it helps
siva

Cross-Docking, Deliveries and availability check

Similar Messages

Maybe you are looking for