STO Document Type (UB) Issue

Dear All,
I am facing a problem in the document type UB. I was copied standard document type 'UB' as "ZUB' and creat STO with the document type ZUB .I was trying to make delivery with MM route (GI in 351 and GR in 101). At the time of making GI in migo screen I got error "This order does not contain items for a stock transfer" Message no. M7153.
But at the same time when I was making the STO with standard document type "UB' it won't through any error and the document was posted properly.
So kindly suggest me the solution with regards to this issue because we can't use the standard one .
Waiting for your earliest response......
Thanks and Regards
AKS
Edited by: Arun3934 on Jun 30, 2011 3:09 PM

Hi
See SAP Note 498143 - FAQ: Stock transfer with delivery in purchasing
For delivery type usually is used the mov 641 for delivery type NL. For cross company you use the mv 643 and del.type NLCC (for cross-company, see SAP Note 109254 - Customizing stock transport order Cross Company, it's the same, change NLCC by NL and forget the billing)
Regards
Eduardo
Edited by: E_Hinojosa on Jun 30, 2011 3:34 PM

Similar Messages

MRP-Exclude STO document type from MRP Run

Hi,
I want to exclude STO document type from MRP run, so that STO Open qty will not be considered as open qty while doing MRP.
I have checked below settings but didn't worked.
1. In OMI8 - I have unchecked "Stock in Transfer"
2. SPRO->Materials Management->Consumption-based Planning->Planning->Define torage Location MRP per plant
     Here I have excluded ONE storage location from MRP and same storage location has been used in the STO.
Can anyone know how to resolve this ?
Regards,
Rakesh

Rakesh,
Yes, they will not be relevant for MRP. Neither will anything else in that storage location. However, the setting is not in configuration, but in the material master (MRP4 tab).
The configuration setting you mentioned has no impact on existing material masters, it is only used to determine the default settings for newly created storage location entries for a material/plant..
You can set a particular material/plant/stlocn to be irrelevant for MRP. This relevancy is irrespective of document type, it can be a STO, a purchase req, a sales order, a production order, or it could be stock (inventory) - all supply and demand in this material/plant/stlocn are excluded from MRP processing.
MRP relevancy of storage location is set at the material/plant/storage location level in the material master.
If you do not wish to exclude a storage location from MRP, then you will have to find another way to make your STOs Irrelevant for MRP. As I said earlier, STOs (like any other Purchase orders that are configured to process stock ), are generally considered to be relevant for MRP.
If you were a client, I would suggest that you rethink your business model that drives this requirement.
If the business model cannot be altered, and the storage location solution is unacceptable, then you will be stuck with a customized solution.
Best Regards,
DB49

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

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.

STOCK TRANSFER DOCUMENT TYPE

Hi Expert
i had made a new document for stock transport order, while making a po for STO i am getting below error.
Message no. 06674
Diagnosis
Settings have been made in Customizing specifying that document type ABCD is normally to be used for supplying plant 6600 and receiving plant 7700. However, you have chosen document type MNOP.
Procedure
Please choose the document type that has beem defined (ABCD).
Further notes
If this message is a warning, you can also continue with the originally chosen document type MNOP. The ordering process will then be handled in accordance with this document type.
Regard
Nabil

Hi,
You have created new document type for STO is MNOP & check the new STO document type MNOP is assigned to Supplying Plant, Receiving Plant or not. If not , just assign in following path:
SPRO --> Material Management -- > Purchasing-- > Purchase Order-- > Set up Stock Transport Order--- > Assign Document Type, One-Step Procedure, Underdelivery Tolerance
Note:
As another document type ABCD for STO is assigned to Supplying Plant, Receiving Plant, so system showing error message.
For more check the link:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4d/2b917843ad11d189410000e829fbbd/frameset.htm
Regards,
Biju K

Need to pull License type from GTS to R3 in case of STO documents

Hi Gurus,
Currently, In standard sales order process, we are using 2 functional modules in R3 to get the ECCN number and license type from GTS. This is required to populate on some billing output.
Functional modules used are:
/SAPSLL/***_DOCS_SD0C_FETCH_R3
/SAPSLL/***_DOCS_SD0C_GET_R3
Using above mentioned functional modules, we can only pull ECCN number and license type from GTS only if we pass sales document number to this FM and further system pulls ECCN and license type from GTS by referring the sales document number.
Issue:
We have a requirement is to pull the License type in case of STO documents also but STO documents/STO deliveries are not checked for GTS check, so we can not use above mentioned functional modules to pull the license type from GTS to R3 because STO/PO / deliveries do not exist in GTS.
I just have the material number with me and I need to pull the license type from GTS to R3.
Could anyone please advise the table name or any structure where i can pass the material number in GTS and can pull the license type to R3.
Your kind response would be appreciated.

Hi DG,
Thanks for your kind response. Regarding your second point, I am already pulling the ECCN number by using one customized functional module so I already have ECCN number with me. Could you please brief me how I can pull the License type linked to an ECCN number. What is the relationship table/ logic for pulling the license type by passing the ECCN number ??
Looking forward to your response.
Regards,
Anoop

Issue With Sales Document Type in BW.

Dear Experts,
I am facing an Issue with Sales Document Type(Object name is 0DOC_TYPE).
when i am loading data from R/3 to BW It is converting Sales Document type as follow
Sales Document Type in R/3                         Sales Document Type in BW
OR                                                                        TA
CR                                                                        G2
DR                                                                        L2
I check with an ABAPer and he told that there is conversion exit for this Object so that's why it is converting when sending to BW. But the user wants to see in Report same as it is in R/3 like OR, CR DR ... etc.
I have done some investigation and found that the conversion exit (CONVERSION_EXIT_AUART_INPUT and CONVERSION_EXIT_AUART_OUTPUT) are converting the values based in the table TAUUM
The staructure of TAUUM is
MANDT(Client) SPRAS(Language) AUART(Sales document type (not converted)   AUART_SPR(Language key for sales document type)
and values are
100 E TA OR
100 E G2 CR
etc....
The same Conversion exits(CONVERSION_EXIT_AUART_INPUT and CONVERSION_EXIT_AUART_OUTPUT) and table TAUUM are available in BW as well. So i thought I can Use InfoObject 0DOC_TYPE by changing it's conversion Routine as AUART(which runs based on the above mentioned conversion exits).
but the the problem is table TAUUM(Pool Table) does't have any data in BW.
So can anyone tell me is there any option to load data into table TAUUM from R/3 or any other option to solve this issue.
Your ideas will really help's me.
Thanks in advance,
Dara.

Hi Venkat,
Thanks a lot for your immediate response.
The InfoObject 0DOC_TYPE was without conversion exit by default. but when data coming from R/3 it is converting and sending to BW So that's why i am planning to use conversion exit "AUART" in the info Object.
I checked data in R/3 using RSA3 it is showing sales document type as "OR" and for the same transaction data when i checked in PSA it is showing as "TA".
Could you please let me know if there any other options.
Thanks in advance,
Dara.

Easy DMS document type issue

Hi Gurus,
DMS configuration done in SAP R/3 and able to see all configured document types in sap easy dms as well. But document description wrongly showing under document types.
SAP R/3                                                       EASY DMS
Eg:1   ZSD sales document                          Eg 1 : ZSD    material document
Eg 2 ZMM material document                      Eg2:   ZMM    sales document.
Please help me on this.
Regards,
Nithal.

Hi Chandu,
Everything fine.
In SAP r/3 , document type & document description correctly given but while in EasyDMS document type picking incorrect document description. Remains no issue in easyDMS.
Please help.
Regards,
Nithal.

Reporting issue on document types

Hi experts,
We have an requirement in the report which is based on a gl cube,
where we need to show all the accounting documents of type DZ and the reversals of only these documents ie RD of only DZ.
RD Documents are not only the reversals of DZ document they can also be the reversals of other document types.
So how to show only RD document for DZ document types.
Please help me on this issue.
Regards,
Nishuv.

Hi Ram,
Thanks for the reply....
So now i need to create a query which brings only accounting documents of document type DZ.
And then create a new query in which i need to create a new variable for accounting document no with replacement path and should give the first query as replace the query with first query result.
And also in the second query i need to restrict document types with DZ and RD.
Is this correct ?
Please let me know....
Regards,
Nishuv.

Assignment field in goods issue/delivery document type WL

Hi,
Would anyone know where we can check how the value for Assignment field in goods issue/delivery document type WL is determined? Any help is greatly appreciated. Thanks.
Sheila

Thanks Samit. We are already aware of the delivery document type. Would this be maintained anywhere in the copy control? We are still not able to determine how the Assignment field is populated in the accounting document of goods issuance. Thanks.

Fbl3n vendor code issue for RE document type

Hi
I entered in fbl3n t.code GR/IR account number then i execute it shows for document type WE (Goods receipt) assignment no,document no,doc type,doc date,vendor code.but in RE(Invoice receipt) document type,vendor code only not display all other datas shown,is this possible to dispay vendor code in RE document type.plz suggest
Regards
Sam

First of all you will have to copy the FM SAMPLE_INTERFACE_00001650 to a Z one .
Then you will have to loop where the offseting account would be blank , then refer the same to BSEG or FAGALFLEXA or Vendor / customer open items .
Then you will have to pass the values in the fields if already there in structre - RFPOS else append the structure and create new fields in structure .
This is how you will have to proceed .
Take the help of an abaper for Code and appending the structure .
Cheers ,
Dewang

Document type issue

Hi,
We use document type SA for multipuspose,customer to customer balance transfer,adjustment in AR,GL postings e.t.c. Now its requirment to use different document type for customer tranfer posting and related adjustments. I want to know the impacts if we change document types and what would be proper document type that should be used for customer related ajustments.

Hi
you should have different document type for different scenarios, more so if you are on new gl, in which document type is the first setting for splitting. Further, ideally, DG is the document type mostly used as std for transfer posting of customers. You can also choose to define your own document types for customer txn.
regards
Sanil Bhandari
<a href="http://www.frostwire.name">isohunt</a>, <a href="http://www.utorrent.name/">utorrent</a>Hi

Document types issue

Hi experts,
We are doing a query on GL Cube. Our requirement is to show DZ documents and the reversals of DZ
documents i.e RD documents How to find RD documents related to DZ documents only ? There may
be chance that reversal documents ( RD ) will be for other document types also.
Regards,
Nishuv.

As per you,
You means to say,
I need to create a infoset, which is based on the gl dso. I need to take again the gl dso into the infoset
i.e i need to use the same gl dso 2 times. Then i need to create inner join with the join conditions:
Left DSO clearing doc number = Righ DSO Acc doc number
Left DSO clearing year = Right DSO year ( let me know which year it is )
Left DSO co code = Right DSO co code
We dont have clearing year in our cube. Can we join it with clearing date ?
In the second method:
Create a new cube for DZs.
I am not clear with the following:
Read in the reversals by a look up to DSO based on the clearing join above
and also in the Note: you will need secondary indexes on the DSO on the clearing to do this
what are the secondary indexes ?
Plz clarify these things.
Regards,
Nishuv.

Issues in creating Sales Document Type

I am creating a new Sales Document Type, but the problem is this that the "Probability" &
"Incompl. Proced" fields are disabled and I am unable to enter record in this field , please help me out that how can I enter values in these fields.

Hi shadab ali
You will be configuring the Incompletion procedure in SPRO->basic functions->Incompletion log procedure.
There to your sales document type an incompletion log will be assigned and that incompletion log will be getting grayed out. So if you want to change you need to change in in Incompletion log procedure. And the probability will be getting grayed out as it is determined by the Sales document category .That is the reason if you see for document type IN the probability will be different and if you see for document type QT probability will be different but if you see for document type OR the probability will be 100%.Generally it gets copied from the CMR also.
Regards
Srinath

Stock Transport Order for Intra Company Code Plants (UB Document Type)

Hi All,
I have a doubt with respect to Intra Company Code Stock Transport Order (Document Type: UB).
When you do Post Goods Issue (PGI) with reference to Outbound Delivery, Accounting Document is generated.
But, when you do Goods Receipt with reference to Outbound Delivery, Accounting Document is not generated.
I am OK with the Receiving part.
But, I am not clear about the Issue part.
Please clarify this doubt.
Looking for the kind respons from all.
Thanks & Regards,
Srinivasa M.S
+91-7387702227

Hi Srinivasa,
In STO, the issuing plant stock is credited and receiving plant stock is debited at the PGI from supplying plant. Then at the receiving plant accounting entry is not generated as the receiving plant stock is already debited at PGI accounting entry in the supplying plant.
Go through the below SAP documentation,
http://help.sap.com/saphelp_oil472/helpdata/en/70/23ccfe419311d2ac100000e829fbfe/frameset.htm
Hope this will solve your issue.

STO Document Type (UB) Issue

Similar Messages

Maybe you are looking for