Plant on WE doc type

Hi gurus please help me with the below issue
Let me explain in detail
we create 2 Purchase orders. during intracompany stock transfer- STO.
1st PO
We have a delivery of goods from one plant to another with a PO from receiving plant to supplying plant.
And this part is woring fine.
2nd PO
For the transporation of the material, SAP creates another PO for freight. And SAP is automatically posting goods receipt on this freight PO. When this posts, a "WE" doc type entry(on the freight PO) is created and when I look into the FI doc for this receipt, I see that there is a plant coming from PO on the credited line item and we are OK with this... BUT on the debit line item on this document, the plant is being populated, and I dont know where it is coming from and I want to know the configuration of populating the plant information on the goods receipt FI doc.
please advise.
Thanks for your time
MSJ

Hi
There may be a substitution active whcih is determining the Plant and substituting in the accounting documents, Please take help of abaper in checking the same.
Thanks & Regards
Kishore

Similar Messages

WRP1 excluding open POs based on doc type

Hi friends,
We are using SAP IS Retail ECC 6.0
In our business, we are having requirement that Open PO quantity of particular document type (eg ZNBA) should be excluded from the WRP1 requirement calculation.
Eg:
For an article 100001, Site A001, following are the details,
Reorder point - 10
Target stock - 20
Current stock - 5
Open PO quantity: (ZPO1 and ZPO2 are PO doc. types)
ZPO1 - 2
ZPO2 - 1
Now WRP gives requirement of article as of 12 quantities.
My requirement is to it should not include ZPO1 open quantity in consideration but should take ZPO2 into consideration.
Hence requirement is to create PO for 14 quantities
How do I achieve this?
We have a control in SAP IS Retail where we can specify, that stock of which storage location should be considered in replenishment requirment calculation.
Do we have a similar control for the PO Doc type? If not, how do I achieve workaround?
Thank you,
regards,
Gaurav

Hi,
Do the Following, Create a new storage location., "ZL01"
Whenever your creating a PO with this "ZPO1" document type assin this Slocation "ZL01", then do the below settings in SPRO..
SPRO->Materials Management->Consumption-based Planning->Planning->Define Storage Location MRP per plant.
(In RP indicatior please give "1"Storage location stock excluded from RP, this will exclude the stk from this location)
Regards
GK.
Edited by: Gnana Kumar on Oct 22, 2010 11:15 AM

Sales doc type

Hi,
If in a business having Plant Sale,Depot Sale & Export slaes then I have to create one sales doc type-ZOR1 for all types of sales & one document catgory & one pricing procedure.,Please give me the solution.
Thanks,
Siku.

Hi,
Can you be more clear with your question?
But in case if you are asking whether you can use 1 doc type and 1 pricing procedure for different kind of sales scenario then answer to that is you can still use 1 doc type for plant/depot./export sales but its not advisable esp for depot sales u should use STO (stock transport order) for which already seperate doc type has been provided by SAP.
Also when coming tp pricing procedure its advisable to have seperate pricing procedures only for domestic/export sales as well as depot sales as the CTs would be varying as in terms of freight, taxes, surcharges etc (as applicable and as per country laws) and you need to take into consideration the excise implications ( or depot sales)
Regards,
Kant

Different Doc.Types for Cash Payment & Cash Receipt

Dear All,
Is it possible to have different doc. type & no.ranges for different plants for cash receipts & cash payments?
Regards
Marcus.

Hi
It is possible to have seperate document types for cash payment & cash receipts.
If you are using normal documetn psoting transaction you can define the document type on your own while posting to the doucment.
If you are using the cash journal, documetn types hv to be specified in the configuration.
VVR

STO UB doc type

HI Gurus,
Can anybody please help me with this? When we are procuring the materials from a different plant using STO.(The config is all setup). Do we need to maintain a source list in the procuring plant with the supplyinh plant as the vendor and also do we need to maintain inforecord. Please help and clarify. Also in the STO config can we have these at the same time
Supplying plant plant (receiving plant) doc type
XXXXX yyyy NB
XXXXX yyyy UB
Thanks
Anusha

You will want to have the supplying plant tied to the vendor (shipping) plant in the vendor master data under the vendor purchasing data screen, and menu path Extras -> Add purchasing data. You need the information record as well. Be sure to have the STO config for the plant and customer plant in the IMG path: Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Define Shipping Data for Plants.
If you have ECC 6, you wish to go even further with "Set Up Stock Transfer Between Storage Locations". This is set up with more integration with the LE/SD modules with shipping points in these areas (Set Up Stock Transfer Between Storage Locations and Define Shipping Data for Stock Transfers Between Storage Locations).
Regards

Minimum order quantity for STO UB DOC type

Hello Guru's,
This issue is regarding STO (UB doc type):-
Client's requisrement is while creating the STO using trax ME21N system should issue an warning message, if the STO line item exceeds the Minimum order quantity mantain in Material master data.
For Standard PO works fine because that we can set it in Info record, but in STO for UB doc type it is not working, since we can't create info record for STO.
Is there any settings availabe in SAP for Minimum order qty for STO (UB doc type).
Thx in advance...
Waiting for valuable inputs
Regards,
Sujoy

Not sure if I know one either,.. however you could always validate it through a user exit. Maintain a Z-table with the order type, Supplying plant and qty filds.. min-max and any other and validate it each time during check and save..

REPORT-TOTAL GR VALUE FOR DOC TYPES MONTHWISE

Dear Experts,
Please help me out for finding how to see the total value of GR for doc types NB and the Assets monthwise..

Hi,
Use ME2L or ME2K standard report.
In ME2L report enter the Purchasing org, Scope of list (ALLES), Plant, Account Assignement category A, Document date.
In ME2K you can see the report for individual asset.
Regards
Karthick

Customisation for PO Release (different Values for different Doc Types)

Dear Experts,
I need to configure for PO release procedure where in the Characteristics would be Plant (2 Plants), Doc Type (3 types - Standard PO, Imports PO & Capital PO) and Value (2 stage release: 0-100000 & >100000 INR for Std PO, 0-200000 & >200000 INR for Imports PO and 0-300000 & >300000 INR for Capital PO).
Please let me know where I shoud define the different Values for different Docs for the Release procedure to work properly.
Or let me know the entire procedure for achieving the same.
Regards,
MNP

Hi MNP,
You have to create different CLASSes in IMG with the possible combination of different characteristics,
EX. CLASS EKKO11 - Plant A, Doc type- Std PO, Value- 0-100000 & >100000 INR
CLASS EKKO22- Plant A, Doc type- Import PO, Value- 0-200000 & >200000 INR
CLASS EKKO33- Plant A, Doc type- Capital PO, Value- 0-300000 & >300000 INR and same for other plant
then assign these classes to the respective Release group.
regards,
Pravin

Partners not defaulting in UB doc type STO

Hi Gurus,
Can anybody please explain why the partners do not default in the partners tab of the PO with doc type UB when i enter the supplying plant. But the partners default in NB doc type when i enter the vendor. Why is this so?
Thanks
Anusha

sto with UB type is meant for stock transfer between plant to plant of the same company code.
There is no vendor this document. This is company's internal functionality.
so there is no question of partners and no required also.
where as sto with NB document type is for plant to plant stock transfer of different company code.
so it is treated as purchase order sent to vendor.

Message No delivery type defined for supplying plant BP01 and document type

Hi all,
I am trying to create a purchase order with a BP01 supplier and the BP02 division but I get the following error message No delivery type defined for supplying plant BP01 and document type.
When I create a PO with a BP02 supplier and the BP01 I do not get any message.
How can I fix it ?
Thanks
Regards
Pierre

1)Create one Customer for Supplying Plant Sales area and assign this Customer no with Receiving Plant in OLME---> PO -
> Set up STO -
> define Shipping Data for plants. and maintain the same sales area in your Supplying plant.
2) In OLME---> PO -
> Set up STO.....for your Document Type: UB and Suppying plant Combination assign Del. Type NL and Checking rule RP
3) In OLME---> PO -
> Set up STO...for your Supplying Plant and Receiving Plant combination Maintain Doc. Type : UB
Make sure you are maintaining Sales View for your Material at Supplying Plant.
4) Maintain Shipping point at, SPRO----> Logistics Execution -
> Shipping -
> Basic Shipping Functions -
> Shipping Point Determination for Plants.....there for your Loading group,Shipping Condition, Shipping Plant combination maintain Shipping plant..
Now Create STO in ME21N with Doc.type: UB at Receiving Plant.
Then Create Delivery in VL10B from Supplying Plant...
Then Do PGI in VL02N from supplying Plant.
Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...

Problem with Doc type change in ME51n

During ME51N, when I change the document type of PR system keeps on Processing/busy mode, takes long time (almost 5min) to effect the doc type change in drop down.
there is no processing time taken if i enter the the other data in the transaction like quantity,Plant,Purchasing organisation.
So my Problem is that system takes too much type only when I try to change the Doc Type of PR in ME51N.
(Note: In debug mode I try to locate the pain point, I noticed that system stuck at module 'Even_pie_finished'...there it keeps on processing continuously.)
Please input on problem. I am putting this on MM forum at times.

Thanks for Reply,
But the Problem is not on changing the Doc type rather Problem is with too much time taken by system when I try to change the doc Type of PR. Prerequisites related to changing the doc type are there in place.
System goes in into processing mode for long time movement I change the Doc type.
Jurgen sir, Dev & Prasoon please suggest some input.
Just to correct in my question module name is 'event_pai_finished'
There must some infinite loop is getting executed in programme i guess.

Multiple doc type setting for service PR generated from Maintenance order

Hi Gurus,
My client has multiple company code and has different document type for PR and PO as per the company code. For generating the service PR from maintenance order system take the document type of PR defined in the config.
Is it possible to define multiple document type for service PR depend on the company code/ Plant level?
Kindly help.
Regards
DP

Hi Ravi,
I used the User Exit COZF0001 . Since we can assign only one PR doc type in the config .
I have assigned one PR doc type in configuration which will work for a company code and all their respective plant. So in this case user exit wont do any job for changing the doc type.
You will defined a condition in the User exit saying that if company code /plant which you get it from maintenance order is not same (Config ) then provide the PR doc type which you want to create for respect plant or company code.
I dont have coding right now with me. You need a small coding to be done to create the separate PR doc type in EBAN-BSART
with respect to plant . Check in your configuration at what point of time you are creating the PR either in saving or release of MO. You can take the even to activate the User exit.
Consult your ABAPer they can do in 10 min.
DP

By default - in STO P.O with UB doc type

Hi,
Experts
When am creating a purchase order with NB doc. type in ITEM level Delivery Tab is there,if i check stock type field it is showing as quality inspection stockas bu default, bcz my material is totally activated with quality management , its ok but in case of STO with UB document type with same material its showing as by default unrestricted stock , why? Manually i can change to quality stock but i want by default it should come as quality stock in my STO Purcase order.
My query is - why in case of UB doc stock type field is showing as unrestricted stock instead of
quality inspection stock
Note- Material is toatally activated with QUALITY MANAGEMENT with both of PLANT.
Thanks
Sunil
09878996821

Hi Sunil
As you are doing STO and you are doing quality check also then first of all check in the NB document type details that by default quality check has to be triggered .Also maintain quality check at delivery level also as you are doing STO
Check in UB document type wheather the first option is unrestricted use, 2nd option is unrestricted and quality check and 3rd one is quality check has been maintained. And in UB document type that feild might have been kept blank that is the reason you can scroll down and see all options. So maintain in UB document type the option Unrestricted use and quality check.
Regards
Srinath

Shipment Cost and Plant Abroad Config Doc

Can anybody provide me with the Step by step
1.Shipment cost configuration Doc.
2.Plants abroad configuration doc.

Hi
Please Follow below steps.<b>Shipment cost</b>
1)Create the transportation planning point for the company codes.
2) Maintain transp. relevance for the dly doc. type, item cat and routes
3) Define the shipment types
4) Define the shipment cost types
5) Define shipment cost item categories and assign
6) Define shipment cost relevance
7) Maintain pricing
8) Assign purchasing data
9) OBYC
10) OKB9
AND Please check the below:
Step1: T.Code: VL01N: Just Create Delivery Note here. Do not do the Picking and Packing.
(This is Client Specific)
Step 2: T.Code: VT01N: Create Shipment.
Here mention your Transportation Point and Shipment Type you Configured for this and Click on deliveries ICON.
GO to W.ref to
Outbound Delivery : Give your Delivery Number that you created earlier for this shipment and F8( Excute)
Then Select the Delivery and Click on OverView
Here Click on Planning then automatically Route( If route determination is done) and Vendor Number get generated and Save the Data.
Step.3: T.Code: VL02N: Change Delivery.Here give the Delivery no and
Do picking, Packing (If necessary) and PGI.
<b>Plants abroad:</b> Sales-specific settings
Description
If plants exist abroad for a company, i.e. in the same company code, (within the EU), the tax postings and the trade statistics for the goods flow between these plants are required for (INTRASTAT) internal EU trades statistics. In SD, this applies to replenishment and consignment.
You can meet these requirements by carrying out billing with special settings in pricing for the relevant transactions:
Because the INTRASTAT declarations were created using billing documents and the tax postings were created using financial accounting documents, billing documents are created for consignment fill-ups or pick-ups and replenishment deliveries although they are not relevant for billing. However, because there are no amounts the billing document has a total value of 0, obtained using a special pricing procedure (see below). INTRASTAT declarations and tax postings (the billing document is forwarded to FI) are created based on the resulting billing documents.
Do not make these settings if the plant abroad is not in the EU. All that is required is a pro-forma invoice.
Change system parameters in customizing
You can find Customizing for 'Plants abroad' in the IMG via 'Sales and Distribution/Basic functions/Taxes/Plants abroad "Plants abroad".)
A special pricing procedure (RVWIA1) is assigned to the new billing document (billing type WIA) defined for replenishment deliveries and consignments between EU countries. This pricing procedure has the following structure:
      1. Pricing condition (PR00)
      2. Input tax in destination country (based on pricing condition)
      3. Output tax in country of departure (that is, 0% on deliveries within the EU)
      4. 100% discount R100 (based on pricing condition)
      5. Output tax in destination country (based on the 100% discount)
This causes the total value of the billing document to be 0. The discount annulls the price. Input and output tax have the same percentage rate so that the total of the tax posting is zero and the total billing document has value 0.
Changes to the interface
Stock transfer
Replenishment deliveries between different EU countries are relevant for billing. The billing status is A.
The origin of the VAT registration number (billing header) has a new value: J
Consignment fill-up / pickup
Consignment fill-ups / pickups between different EU countries are relevant for billing. The billing status is A.
The origin of the VAT registration number (billing header) has a new value: J
During consignment fill-up, the coutry of the ship-to party is now used as the departure country country for tax determination.
Changes in procedure
Deliveries that occur as a result of a stock transfer order, can be billed if the delivering and receiving plants are in different EU countries and belong to the same company code.
Consignment fill-ups and pickups can be billed if the delivering plant is in an EU country and the consignment stores are in a different EU country. The consignment fill-up is then no longer relevant for the INTRASTAT declaration.
Condition records must be created for tax conditions WIA1, WIA2, and WIA3.
      1. WIA1: Input tax in country of destination.
      The tax code for the tax determination procedure of departure country must agree with the tax code of the country of the company code. This is because the tax code is accessed via the company code country during forwarding to FI. The field 'reporting country' (that is - country of destination) must be maintained in the characteristics of the tax code.
      2. WIA2: Output tax in the country of departure (0 % for EU-internal deliveries)
      3. WIA3: Output tax in country of destination.
      The tax code for the tax determination procedure of departure country must agree with the tax code of the country of the company code. This is because the tax code is accessed via the company code country during forwarding to FI. The field 'reporting country' (that is - country of destination) must be maintained in the characteristics of the tax code.
The total of the taxes has a value of 0. The total of the billing document also has a value of 0. The price is reduced by 100% using discount R100.
Procedure for removing dataset errors
Note:
When you maintain the tax indicator, remember that the tax indicator must be maintained at the same time in different tax determination procedures, or that you have to create a general tax determination procedure containing the tax indicators of the different relevant countries.
Please read the Release Note
abroad.
Dependent functions
INTRASTAT declarations, combined declaration, Sales tax advance return
http://sap.ittoolbox.com/groups/technical-functional/sap-acct/plant-abroad-functionalty-66840
SHESAGIRI.G
Message was edited by:
        SHESAGIRI.G

Configuration for new po doc type

Hi guys,
We are on a roll-out project. We want to use new doc types for Purchase Orders and scheduling agreements for the new plant. What are all the configurations required for printing of these new doc types?
Thanks in advance,
Chintu

Hi chintu,
If you have copied new document type NB, No specific configuration is required , maintain a condition record in MN04 for your document type it will generate print based on settings in MN04, if you give out put to be triggered with own transaction use ME9F for taking print out, if you use immediate o/p in Mn04 , once you save the PO it generates a Print
Settings required to trigger the output/type
Copy Message type NEU and create your OWN , and assign new form to this message type , insert this message type in Message Schema
Below is the path :
SAP Customizing Implementation Guide >Materials Management>Purchasing>Messages>Output Control>Message Types>Define Message Types for Purchase Order : Here you can assign your new form and maintain all the setting like NEU
Message Determination Schemas -->Define Message Schema for Purchase Order
Insert your message type here
In order to trigger the Print at document level automatically you have to maintain Condition records
Hope it will help u
Regards
Hareesha

Plant on WE doc type

Similar Messages

Maybe you are looking for