One/Two Step STO by Document Type

Hello,
We have a requirement where we would like to use two different (UB) STO document types, one utilizing a one-step STO the other a two-step STO for the same supplying / receiving plant combination. We have different delivery types associated with the two STO document types.
The standard configuration appears to enable/disable one-step for all document types between that shipping and receiving plant combination.
I was hoping to create a new schedule line assigned to a new item category for the one STO type which has the 641 movement type removed, but when I try that the delivery is not being distributed to out decentralized WM system.
Thoughts or other approaches?
Best,
Matt

I was able to solve this as I was on the right route with schedule line category. I have created a new schedule line category which in turn is assigned to my item category, delivery, and STO document type I wish to use for the one-step STO. I that schedule line configuration I have specified both the one-step and two-step movement types as 647.

Similar Messages

How to get one column value from a DOCUMENT TYPE attribute

Hi,
I have created a DOCUMENT TYPE attribute which queries from a table and all the column values( For Ex: Customer Name, Contact Name and Address) are displayed in the message body.
I want one column value(For Ex: Customer Name) to be displayed in the SUBJECT of the message.
How can this be done? Please let me know.
Thanks in advance.

Thanks Matt. I have used SETITEMATTRTEXT to get a single column value into an ITEM ATTRIBUTE.
Please see the following procedure...
==========================================================
PROCEDURE MisNotifyDataDesk(
     itemtype IN VARCHAR2
     , itemkey IN VARCHAR2
     , actid IN NUMBER
     , funcmode IN VARCHAR2
     , resultout OUT VARCHAR2
     ) IS
p_Cart_Id               VARCHAR2(30);
p_ORG_NAME                     VARCHAR2(360);
BEGIN
     IF funcmode != WF_ENGINE.ENG_RUN THEN
          wf_log_pkg.string(5,'Notify_Cust_Data_Desk','Not in RUN mode');
     RETURN;
     END IF;
p_Cart_Id := WF_ENGINE.GetItemAttrText ( itemtype => itemtype
, itemkey => itemkey
, aname => 'CART_ID' );
p_code_position := 10;
     SELECT
          ORG_NAME
     INTO
          p_ORG_NAME
     FROM
          MISIBE_END_CUST_DETAILS
     WHERE
          QUOTE_HEADER_ID = p_Cart_Id;
-- For TEXT BODY
WF_ENGINE.SETITEMATTRTEXT(itemtype => itemtype , itemkey => itemkey , aname => 'ORG_NAME',avalue => p_ORG_NAME);
resultout := WF_ENGINE.ENG_COMPLETED||':'||CUST_DATA_CHECK(p_Cart_Id);
EXCEPTION
     WHEN OTHERS THEN
          WF_CORE.context (
          'WFCustCheck',
          'MisNotifyDataDesk',
          itemtype,
          itemkey,
          TO_CHAR(actid),
          funcmode,
          SQLERRM
RAISE_APPLICATION_ERROR (-20005, SQLERRM);
===========================================================
I am using &ORG_NAME in the body and subject of my message. But the value is
not retrieved into the ITEM ATTRIBUTE when I run my process. It is just displaying in the message and the subject of hte message as "&ORG_NAME"
CUST_DATA_CHECK used in the resultout, is a function which returns 'T' or 'F'. That part is working fine. Just retrieving the ORG_NAME in the ITEM ATTRIBUTE is not working.
Am I going wrong somewhere? Please let me know.
Thanks,

Intra company STO(UB Document type)

Hi All
We have a problem with STO please see the details below.
We have created STO PO with qty 160 with 5 batches.
Created a delevery wrt to the PO for qty 160.
PGI was done for the delivery.
Did the GR(101 mvmt) wrt to the out bound delivery for 160 qty.In po history in the field reference it is showing out bound delivery number for the above material docs.
After a day GR was cancelled with movement type 102 for the material document which we have created with mvmt 101. But in the reference field it is not showing any thing.Above procses was done in the year 2004.
Now we are trying to cancel the cancelled the material document( mvt type 102)it is giving the error " Document flow for the delivery can not be updated and we are not able to save the document.
The reason why we are doing all the exercises is to close the po, that is already 160 qty was issued by supplying plant now we want to receive the same to receiving plant.
Now all the stocks atre showing in stock in transit (MB5T).
Please help.Urgent
Regards,
Manik

Hi
please find below OSS Notes which is related to your problem.
Summary
Symptom
The system generates message M7352 'Document flow for delivery cannot be updated'.
This is no program error but the meaning of the message is not clear.
Additional key words
Stock transport order, shipping notification
Cause and prerequisites
The system displays message M7352 during goods receipts for deliveries if the following two requirements are met:
You created a delivery for the stock transport order (entry in table EKPV).
The goods movement does not refer to the delivery.
When is the system unable to determine a delivery and thus unable to update the document flow?
You post the goods receipt with reference to the purchase order or to an inbound delivery and not with reference to the delivery
or
You cancel a material document for which the system can no longer find the original delivery. This can occur if you have entered a delivery note (field MKPF-XBLNR) manually during goods receipt.
(As of Note 358454, the system tries to find the delivery using an index on table VBFA. Before Note 358454, the cancellation must be posted via Transaction MB0A/MIGO with reference to the delivery).
Solution
It is not required to implement all corrections concerning M7352 because the message is correct in most cases. With Note 358454, the system tries to find a delivery for a material document even if none is entered manually. However, the note is not absolutely necessary if you already enter all goods movements with reference to the delivery.
Why is the message output at all if it is not an error?
The message can be set as a warning message or as an error message or it can be deactivated. It informs you that the document flow is not updated what can lead to follow-up problems with the delivery.
Check your business process for stock transport orders:
If the update of the goods receipt posting is important to you, set the message as an error message.
If you have no use for the document flow update during goods receipt, you can set the message as a warning message or deactivate it completely.
please check let me know
regards
Srinivas
reward if it is helpful

Two Step Posting in Movement Type 201 and 309

Hi Experts,
Our copmany wants to use movement type (T-code MB1A) 201 and (MB1B) 309 in two way posting, like 313/315 like some body create the document and then somebody apporves the document then finance entry takes place.
How can we map the same in the system, please suggest, its most urgent.
Regards
Ishu

201 Goods issue for a cost center
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators:
K: Goods withdrawal from consignment stock
P: Goods withdrawal from the pipeline
If you have withdrawals from consignment stock and from pipeline, payables to suppliers ensue.
309 Transfer posting material to material
The quantity is posted from unrestricted-use stock of the issuing material into unrestricted-use stock in the receiving material.
Prerequisite: both materials have the same stockkeeping unit.
Possible special stock indicators:
E, O, Q, V, W
I think it is not possible in Standard System

Two Interface with same IDOC sperated by Document Type

Hi All,
I have Two interface which is for RFQ and Purchase order, bother uses same IDOC orders05, i need to indentify which one for which interface using Document type for purchase NB and and AN for RFQ , please help me to slove this isssue , hope we muct use Context object for this , but i dont know how to use it , please help me
thanking you
Sridhar

Hi,
Can you explain a bit about your scenario, coz I think it can be handle in other way without using context objects..
But if you want to use the context object, then you can add it in Message Interace ---> Context Objects, and in ID while doing RD you can find it under Condition Editor ---> take F4 help and then select context objects.
Regards,
Sarvesh

One particular Po document type with reference to one particular PR documen

Dear all
I want to create one PO for a particular document type only with reference to one PR, that to after release of PR, how can i do it.

Hi
Goto, OLME ---> PO ---> Define Document types -
> Choose your PO Doc.Type...> there in Linking PR and PO Doc.Type....allow your PR doc.Type only.....
Also in OLME -
> PR -
> Define Document types -
> Choose your PR Doc.Type...>There also you maintain this PR Doc.type only as ref. to your PO doc. type....
Then Configure Release Statergy in such that All your new PR Doc. type PRs should gone thro the Release Statergy.....(use field CEKKO-BSART)
Reward if useful
Regards
S.Baskaran

Multiple STO document types conflict in ME59N

Folks,
I have the following scenario's:
1) PReq NB with item category U -> intercompany STO NB (depends on the supplying and receiving plant) document types gets determined correctly through STO document type customizing (T161W)
2) Preq NB with item category u -> intracompany STO UB, document types gets determined correctly through STO document type customizing (T161W)
3) exception flow where preq ZF gets created through a development. This is also inter- and intracompany traffic. In case it's intercompany it should get ZF1 and in case it's intracompany it should get ZF2.
I've set preq - PO linkage that ZF preq can be linked to ZF1 and ZF2. Now when running ME59N, it seems that system only takes settings of T161W into consideration and wants an NB document type and this is not allowed (preq - PO linkage table).
Any suggestions how to set up scenario 3?
MZ

Hi,
Please read OSS note 114213.
http://www.sapfans.com/forums/viewtopic.php?t=237357&highlight=&sid=a33e51e7989bd52296035460ee048409
Regards,
Csaba

Document types - PO

Hi,
What could be the use of defining two or more z-document types for standard purchase orders. What are the factors influenced by document types.
Thanks and regards
Aparna

Hi,
When purchasing process is different then standard one, you can use different document type concept to differentiate the different process of procurement. Example standard procurement process different from Stock Transport Order process, sub-contracting process, so here you can use different document type.
Also you can have different document type may ZNB for purchase order WRT contract. Also you can drill down Contract with Purchase Order to ZNB (centralized purchase order WRT contract) and YNB (Decentralized purchase order WRT contract)
You can have different number range for a process & you have to define a different document type. The other standard document type are:
NB Standard Purchase Order
UB Stock Transport Order
FO Frame Work Order
Regards,
Biju K

Configuring Document Types by Ledger

There are 3 configuration steps for configuring document types:
1) Define Document Types in Entry View
2) Define Document Types in Entry View by Ledger
3) Define Dcoument Types in General Ledger View
What is the purpose of each step and how would I go about creating unique document types that would only be posted to in specific ledgers and have their own unique number ranges?
If I needed to create a document that posts across all ledgers can I just do step 1 and skip steps 2-3 for those document types?

Hai Hari
Define Document Types for General Ledger View
In this IMG activity, you define for Non-leading ledgers the document types for the documents in the General Ledger view. At the same time, you assign for each document type a number range to be applied in the assignment of document numbers:
u2022     You do not need to make these settings for your leading ledger because, in the case of this ledger, the document number in the entry view always corresponds to the document number in the general ledger view.
u2022     You only have to make these settings for any non-leading ledgers that have a fiscal year variant that differs in at least one company code from the fiscal year variant of the leading ledger in this company code. In this case, the document number in the entry view does not correspond to the document number in the general ledger view and you have to define a separate document type with document number assignment for the general ledger view.
For all non-leading ledgers that, in the company code to which the postings are made, have a fiscal year variant corresponding to the fiscal year variant of the leading ledger in this company code, the document number in the entry view always corresponds to the document number in the general ledger view.
Note
The need to define a document type for documents in the general ledger view depends only on whether the fiscal year variant of the non-leading ledger in the company code (to which the postings are made) differs from the fiscal year variant of the leading ledger in this company code. On the other hand, document type definition is independent of which the type of ledger group to which postings are made, that is, regardless of
o     Whether postings are made without a ledger group
o     Whether postings are made to a ledger group with a leading ledger as the representative ledger
o     Whether postings are made to a ledger group with a non-leading ledger as the representative ledger
Define Document Types for Entry View in a Ledger
Here, you make the settings specifying the document type for postings to non-leading ledgers.
Under Define Document Types for Entry View, you make the document type settings for postings in the entry view that effect all ledgers and for postings to the leading ledger.
Requirements
You work with a leading ledger and with non-leading ledgers.
Activities
To define document types for postings to non-leading ledgers, proceed as follows:
Set up a separate document type for these postings. Assign a unique number range to this document type for each ledger.
Example:
Document Type SX, Closing Postings, Ledger L2, Number Range FI
Document Type SX, Closing Postings, Ledger L3, Number Range FI
Note
By segregating the ledger-related postings (here, for the non-leading ledgers) in a separate number range, you ensure the contiguous assignment of document numbers at the ledger level for each number range.
Within a ledger group, the representative ledger determines the document types and number ranges applied. For this reason, you cannot perform this IMG activity for a ledger group.
If you use a ledger group to make account assignments for postings, it is only possible to verify that document numbers are assigned contiguously at the ledger level for the representative ledger.
Regards
Madhu I

How to Customize a document type to use on CV01N transaction in SAP

I am trying to create a attach document in CV01N but I want to set up a new document type and don't want to use existing ones, so can some one help me in how to configure new document type and also please tell everything in step by step in order to xcomplete this process successfully.

HI,
1. Define Number Ranges for Document Numbers
T code OD00
SPRO / IMG -> Cross - Application Component -> Document Management System -> Control Data -> Define Number Ranges for Document Numbers
2. Define Document Type
T code DC10
SPRO / IMG -> Cross - Application Component -> Document Management System -> Control Data -> Define Document Types.
In this step, you create Document Type for categorize documents according to the organizational procedures.
Supppose u define ZAD
Document Type The document type is used to categorize documents according to the organizational procedures. E.g. in company, there exists many departments for which separate document types have been created. For example, ZAD,ZCB,ZCD etc Document type is a three digit alphanumeric field.
Document Type Description Description appears in the screen heading when document info record is being processed.
Use Kpro Indicator controls that the original files are stored in defined content repository via Knowledge Provider.
Assignment of Revision Level This indicator shows that a revision level is automatically assigned to a document the first time the document is released with reference to a change number.
CM Relevance u2018 u2018 u2013 Not Relevant for Configuration Management
u20181u2019 u2013 Relevant for Configuration Management
Determines whether Configuration Management controls the object.
Number Exit MCDOKZNR Program that controls number assignment and version numbering for documents.
Regards,
Pardeep Malik

Assignment of billing document type with accounting document type

Hi
I need one information regarding SD Billing Document type assignment with accounting document types.
Here CRM people asking me where we can see if the Billing doc type is BV( Cash Sale) accounting document should be RV
Just go to T.Code VOFA for Billing document types. Based on this only system generate the Accouning documents RV, AB so onu2026u2026.
But how it is determining this accouning document type they want to know.
Pls advice

In VOFA where it says Document type enter the FI doc type they want to post to. Otherwise it defaults to RV.
pls assign pts to say thanks.

Document type Authorisation in FBL1N

Hi Friends,
We have one requirement to restrict the Document type authorization in FBL1N for one user.
Since in SAP we have created the employee as the Vendor so we are passing the salary voucher vendor wise.
We have tried to check the the authorization object through SU24 for transaction code FBL1N and found the F_BKPF_BLA after that, one authorization group is assigned to Document type in OBA7. there after, in table TBRG the authorization group has been assigned to authorization object. Now that authorisation group is being removed from the user id.
but the same is not working.
Please help.
Thanks in advance !!

Hi Janeet,
You can able to restrict those values in 2 methods.
1. Create document type authorization object in OBA7 and exclude this authorization object to business user through mentioned object F_BKPF_BLA
2. Create separate account group for Employee vendors and assign one authorization group in Vendor master and restrict those values in FBL1N through authorization object F_BKPF_BEK
You have to exclude those object from obhjects.
Regards
Mani

Separate PR document type for material from PS

WE need to create two separate material PR document type for example WBS level-1 and WBS level-2. How can I achieve it.Any user exit or what is the simplest method.
Zinni

Hi
Thanx. My project having two separate WBS element for which import trading material is required and some material required during installation , mostly consumable materials. Two separate document type is required for the purpose.
Please give me logic how can I assign two document type for two separate WBS element.
Zinni

Requirement for changing document type

Hello Gurus,
       when I want to change sales document type, there is a requirement as following :
" When you change the sales order type for a sales document that has already been saved, both sales document types must belong to the same number range."
my question is:
   1. can sales order type be changed ? most recommend to remove previouse sales order, and create new sales order with another sales order type.
   2. what does " the same number range" mean in the above quoted word ?
thanks very much

Different Order Type can share the same number range. In the case, if Sale Order Type is saved in Transaction, then it cannot be chaged.
The number range is controlled through Number Range Object, which is maintained in Sales Order Type (T.Code: VOV8).
Configuration steps are as under:
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
Note: Ensure that Copy Control settings are done
Sales Order to Sales Order (QT --> OR): VTAA
Sales Order to Delivery (OR --> LF): VTLA
Sales Order to Billing (OR --> F1): VTFA
Delivery to Billing(LF --> F2): VTFL
Billing to Sales Order (F2 --> RE): VTAF
The configuration differs from scenario to scenario & requirement of the client.
Regards,
Rajesh Banka
Reward point if useful.

Two Heirarchy against one document type

I have requirement to run two parallel hierarchy against one document i.e. Purchase Requisition is document type and 1st hierarchy is PR APPROVAL and 2nd is OGP APPROVAL...
Is it possible, if yes than how?
Thanks and Rgrds,
Rizwan

Hi,
Look for AME option.. I think through AME you can handle Parallel approval.
/ S.P DASH

One/Two Step STO by Document Type

Similar Messages

Maybe you are looking for