WorkCenter/plant at Operations level vs WorkCenter/Plant @ Header level

Hi,
We have the following issue:
We use one workcenter but different plants. Workcenter has been created for each of these plants - Eg. Workcenter "Service" for plant XXXX, Workcenter "Service" for plant YYYY, etc. A user creates a service order where the main workcenter is 'Service" plant is XXXX and saves the order. He comes back later and changes the main workcenter plant to YYYY. He does not have to change the workcenter itself since the workcenters all are the same. However, the first operations plant on the order still shows as XXXX and does not change to YYYY as expected. All other rows of operations have plant YYYY.
Is there a way(through config or enhancement) to change the first operations plant when the main workcenter plant is changed? If so, can you pls provide the details.
Thanks.
Regards,
Tim

Hi,
If you are using MB1B , in that case Receving plant needs to be entered only once for while document.
If using MIGO , In item overview select the Destination plant in the 1st line item of the document & click on "Content "Symbol,
It will copy value of the 1st line item to all the below fields .
Hope this serves your requirement.
Regards
Manish
Edited by: Manish Kumar on Dec 2, 2010 12:40 PM

Similar Messages

Delivery address appearing at Item level and not at Header level in PO

Hello Experts,
We are facing an issue as described below:-
We are in SRM 7.0 using classic scenario.
After approval of multi line Shopping Cart in SRM ,PR's are getting
automatically created in backend R/3 system.After converting PR's into
POs in backend R/3,we are observing that the delivery address for these
PO'are getting printed at Item level and not at the Header Level
inspite of the delivery address being same for all the Item level.
As desired,the delivery address in the PO's should have the delivery
address at the header level if the the delivery address is identical
for all the Item Levels.
However,if we create a PR directly in R/3 system and then convert these
PR's into PO's in the backend R/3 system,we find that the deliver
address are getting printed at the Header Level if the delivery address
is same for all the item level(which is as desired)
Any pointers will be highly appreciated.
Thanks & Regards,
RKS

HI Paul,
Thank you for your response.In our case even if all the Line/items level have same Plant and storage location still the delivery address is getting printed at Item level and not at Header Level and this is happening only for PO's created from PR's orginating from SRM7.0.
However if we create PR's directly in R/3 and then convert them into PO's,the delivery address is getting printed at the Header level if the delivery address is same for all the Item level.
Can you plz some insite into this?
Your help will be highly appreciated.
Regards,
RKS

Pricng not getting distributed at item level when given at header level-

Dear all
We are using pricing procedure in Delivery for certain freight condition types...
When a condition type ZFRT is given manual pricing at header level,it is not getting distributed equally at item level..
Can u tell us what exactly the problem..
The same condition type while using in Sales order,distributes pricing to all items ...when given at header level...
Group condition tick mark is put.Priicng is at header level tick mark is put..

Hi,
Go to header level of the delivery document and in conditions tab press "update" and do carry out new pricing and then give the header condition value and press activate.
Reward me if it helps.
Regards,
kishore.

Delivery address at Item level and not at Header level in PO

Hello Experts,
We are facing an issue as described below:-
We are in SRM 7.0 using classic scenario.
After approval of multi line Shopping Cart in SRM ,PR's are getting
automatically created in backend R/3 system.After converting PR's into
POs in backend R/3,we are observing that the delivery address for these
PO'are getting printed at Item level and not at the Header Level
inspite of the delivery address being same for all the Item level.
As desired,the delivery address in the PO's should have the delivery
address at the header level if the the delivery address is identical
for all the Item Levels.
However,if we create a PR directly in R/3 system and then convert these
PR's into PO's in the backend R/3 system,we find that the deliver
address are getting printed at the Header Level if the delivery address
is same for all the item level(which is as desired)
Any pointers will be highly appreciated,
Regards,
RKS

This may be an old note, but it may point you in the right direction: Note 450425 - Delivery Address creates individual R/3 address number.
If you debug the function module in SRM that creates the PO in ECC, you can check if this is the case.
Regards,
Robin

Conditions on RFQ Header are not changeable at PO Header level

Dear Gurus,
I have maintained a Quotation and enter the conditions on Header level in Quotation. Once i adopt the Quotation in Purchase Order, these conditions are displayed both at Item and Header level and i cannot edit the condition value at PO Header level, they are editable at Item level but not at header level.
I want to edit them at PO Header level too.
Please advise.
Johi Kapoor

Hi,
If that is item condition then you can not change it at header level
check in M/06 make it at header level in change which can be made tab
Regards
Kailas Ugale

Rounding at Header Level in Sales order

Hi all SD Expert,
Question:
Can rounding mechanism be applied at Header level in Sales Order?
Summary:
The government of Malaysia have implemented the rounding mechanism to the nearest multiple of 5 cents over the counter transaction. This mechanism shall apply to the total amount of a bill.
Example:
- $1.01 or $1.02 will be rounded down to $1.00
- $1.03 or $1.04 will be rounded up to $1.05
- $1.06 or $1.07 will be rounded down to $1.05
- $1.08 or $1.09 will be rounded up to $1.10
refer http://www.bnm.gov.my/index.php?ch=209&pg=657&ac=567 for more info
My Problem:
SAP Note 1165950 suits well enough for 1 item per sales order.
Example:
Total Bill = $1.38 (posted to a dedicated G/L account)
Rounding Adjustment = +0.02 (posted to a dedicated G/L account)
Total customer to pay = $1.40
But, if I have 2 or more item per sales order, my rounding mechanism does not meet the requirement. Example:
Item 1:
Total Bill = $1.38 (posted to a dedicated G/L account)
Rounding Adjustment = +0.02 (posted to a dedicated G/L account)
Total customer to pay = $1.40
Item 2:
Total Bill = $1.38 (posted to a dedicated G/L account)
Rounding Adjustment = +0.02 (posted to a dedicated G/L account)
Total customer to pay = $1.40
Total Item 1 + Item 2 shown in header level = $2.80
In Header Level, the rounding figure shows +0.04 (rounding adjustment item 1 + item 2). I dont want my sales order to round the value at item level.
The correct calculation to suit the regulation is:
Item 1 + Item 2: $1.38 + $1.38 = $2.76
Rounding Adjustment at Header: -0.01
Total customer to pay = $2.75
can someone help me?
TQ
Ezwardi

Dear Tengku
Please try with this.
Go to V/08, for the net value field, maintain Routine 16 in the Alt. Cal. Type. Also add Routine 17 to Netvalue.
As you know Condition types are assigned at each item level. So rounding off is calculated at each item level. But by assigning a tick in the Group Condition while defining Rounding off Condition, you can do rounding off at invoice level. The difference is automatically adjusted at each item.
thanks
G. Lakshmipathi

PO HEADER LEVEL의 TOTAL AMOUNT 계산 LOGIC

제품 : MFG_PO
작성날짜 : 2004-10-13
PO HEADER LEVEL의 TOTAL AMOUNT 계산 LOGIC
==========================================
PURPOSE
Purchase Order 화면의 Header level에 보여주는 Total Amount 계산 logic을
알아본다.
Explanation
Purchase Order 화면에서 PO를 입력하거나 조회해 본 사람은 PO Header level
에 보이는 Total amount 값은 어느곳에도 저장되지 않는다는 것을 확인 할
수 있을 것이다.
이 header level total amount 계산 logic은 다음과 같다.
1.Purchase Order 화면에서 price와 quantity가 입력될 때 POXPOPOL.pld에
있는 maintain_po_total이 불려진다.
이 maintain_po_total procedure는 line amount를 뿌려주기 위해 line에
정의된 quantity와 price를 고려한다.
이 line amount sum 되고, header total에 뿌려준다.
sum(round((quantity*unit_price),precision))-> Header_total
2.PO를 query 할 때 header amount를 조회하기 위해 POXCOCOB.pls의
po_core_s.get_total procedure가 불려진다.
아래의 query가 PO header level total amount 계산을 하게 된다.
SELECT sum(round((pll.quantity - nvl(pll.quantity_cancelled,0))*
nvl(pll.price_override,0),x_precision))
FROM PO_LINE_LOCATIONS PLL
WHERE PLL.po_header_id = <<po_header_id>>
AND PLL.shipment_type in ('STANDARD','PLANNED','BLANKET')
여기에서 precision은 PO.(PO Currency = Functional Currency)에서 사용
되는 것으로 fnd_currencies에 정의된 currency이다.
Example
Reference Documents
Note 226697.1

Thought so.
And therein lies your problem.
You should avoid updating Oracle tables directly unless you are 100% sure that no relationships are getting violated.
Updating po line price should be done via interface. I would suggest that you use the po documents interface to change the po line prices. Then you will see the header totals get updated automatically.
Hope this answers your question
Sandeep Gandhi
Independent Consultant
513-325-9026

Copying Header level Billing Plan to Item Level Billing Plan

Hi Gurus,
I have the following Business Scenario:
I am creating Sales Order with reference to contract. In the sales order item level detail, a check box(Copy Header level Billing Plan to item level Billing Plan) is checked. For my Business Scenario, I do not want this check.
Could you please help me in making the configuration changes to remove this check box.
Regards,
Nish

Dear
I hope just try once
When you assign Copy Header level Billing Plan to item level Billing Plan That header level billing plan data also will come to item level it means you can change in item level
if you dont want this function in item level -- Billing plan ..Just remove the check box
Then you cant find please try it and let me know
Thanks a lot
venu

ED not captured at header level

Hi
I have created condition record for excise duty with JMO2,but at the time of GR,Ed is is capturing at item level but not at header level
Can anybody solve this isues

Check weather the condition record is created in such a manner it is acceptable in header level also,

AP:GL date stored at invoice header level-11i

In 11i, the GL date is stored at the invoice header level rather
than being a system default field. Once entered and saved, can
the GL date be modified at the invoice header level? Does the
header level GL date automatically get updated when someone adds
or adjust one of the distribution lines, and uses a GL date
different from the original date? Or does the user have to
update the header level GL date manually?

Hi,
While entering the invoice you can change the liability account on invoice header, if the filed is not displayed check in folder options (folder->show Field->Liability Account)
Thanks,
Vijay

Heading level hierarchy errors when topics are in TOC more than once

I have discovered that the hierarchy in the Heading levels in
the Printed Documentation will differ from than in my online help
table of contents hierarchy, and that the problem is due to topics
that are intentionally in the TOC more than once.
For example, in chapter 5 of a particular help system the
hierarchy should be:
Heading 1 < Chapter 5 title from top-level book>
Heading 2 <title of second level book>
Heading 3 <title of topic that appears under second-level
book>*
What I actually get is:
Heading 1 < Chapter title from top-level book>
Heading 2 <title of second level book>
Heading 4 <title of topic that appears under second-level
book>*
* This same topic appeared in an earlier chapter. In that
chapter it was really at a Heading 4 level.
Due to company styles, etc. we use a numbering system at the
headings and in the TOC, so instead of
5
5.1
5.1.1
I erroneously get
5
5.1
5.1.1.1
This type of hierarchy issue appears multiple times in this
particular document (which I inherited by the way.)
Other than restructuring the document to not reuse topics in
different places in the TOC, is there a solution or a workaround
for this problem?
What I am doing so far, is generating the Print Documentation
one chapter at a time. As long as a topic is not reused with the
same chapter, my hierarchy of heading levels is maintained;
otherwise, it is not. Then I can put the chapters back together
after fixing the few places that still have heading level problems.
This however, will be quite cumbersome as this document is
translated into nine other languages.
I am using RoboHelp X5 for Word / Word 2003 for the source
and most of the translations; RoboHelp Asian Edition, Simplified
Chinese / Word 2003 for the Chinese translation. The heading level
hierarchy error occurs in both versions.

>> AF: I've commented in sections...
Without Maintain Heading Levels, RH will apply heading levels
to the books and then the topic levels will get bumped down. So a
top level book will be Heading 1 and the Headings in the topic will
get bumped down to 2, 3 and 4 etc. If then you have another book
one level down so that it gets Heading 2 applied, the same topic
but under the level two book would then get 3, 4 and 5 applied.
That is not the original problem but hopefully we are agreed
that is how things work on that.
>> Yes - that is the expected behavior. When it didn't
happen as expected, that's what led me to the discovery of the
cause of the problem (topic reuse).
Your problem was that firstly Heading 3 got bumped to Heading
4 if the same topic was inserted into the TOC twice. I assume it
was OK in the first instance, or is it that when you add it twice
it goes wrong everywhere?
>> Your assumption is correct. First occurrence is
correct. Second, third, and fourth (yes - there is one topic that
is used 4 times! ) are not correct based on TOC hierarchy.
On the numbering, nothing surprises me. If you look at my
site you will see that for RH HTML, i gave up on getting it right.
I have had many queries on this and more than a few people have
indicated they will work on the problem and get it working. I'm
still waiting. There are many posts about outline numbering
problems. Has anyone got it working satisfactorily?
>> I don't really have numbering problems. The
numbering is following the RoboHelp-generated hierarchy and the
.dot template that I apply. It's just that the RH-generated
hierarchy and its heading levels don't correspond to the "real"
hierarchy because of the reuse issue.
I have seen various Word gurus maintain that numbering has
not worked entirely satisfactorily since Word 2! Also enough posts
to convince me this is a Word issue, not a RH issue.
If you want to create a new project and knock something up
that demonstrates this problem, by all means zip it up and send it.
I'll assume it will be a small project and zip to less than 5mb. If
more, contact me first.
>> Unless you have RoboHelp X3 Asian Edition,
Simplified Chinese, there is really no need. I plan to either avoid
the reuse issue in the source, or build the print doc in sections
which is easy enough in RoboHelp X5 for the non-Chinese languages.
It is in the older Asian edition where the problems are compounded
by the omitted reuse topics. If you do have RoboHelp X3 Asian
Edition, Simplified Chinese and want to experiment, I can send you
a cut-down version of the project. Don't feel obligated though;
unless you can read Chinese (I can't) it is very tedious to work
with.

WM-Prod Issue--Plant NM Company NM and WorkCenter NM02 Company is different

HI
I did material staging and proceed ,i try to save the production order , but i have error like
"Plant NM Company NM and WorkCenter NM02 Company is different"
Message no. ZPP 165
where i missed the configuration .
with regards
dinesh
Edited by: code acess on Oct 7, 2011 11:54 AM
Edited by: code acess on Oct 7, 2011 12:00 PM

ZPP is a home made message class.
Please ask your programmer what he checks and then you will know what you missed

Automatic Plant determination logic in the order line item level

Dear all,
I would like to know if there is a possibility to determine plants automatically, avoiding the standard plant
determination logic at line item level, to determine plant based on stock availability.
The process will be to skip the standard plant dtermination logic and drive the process through
based on ATP on plant level.
Coming more specific to the requirement the system determines the plant where the stock is available and if the stocks are not
sufficient the system goes to the next plant automaticaly and confirms the stock quantities, which also could mean that the ATP would run on plant 1 and then plant 2 and plant 3......depending on the availability of stocks with partial confirmations or full.
If there are existing user exits etc. available also when the configuration not available would welcome it.
Thanks

Hello
On more option I can see is of maintaining preferred plant in Table OIDAP.
Generally, this table is used for IS-Oil plant determination.
There you can set up one preferred plant and up to four alternative plants for a combination of
- sales area
-country
-transport zone (of the ship-to party)
-material number or material group.
The plant selected depends on the availability of material in the plant/storage location.
Regards
JP

Goods Issue to increase the stock levels in a plant

Folks,
I am not a MM guy and I am trying to increase the stock levels in a plant using a Goods issue.
1.     Can I do the Goods Issues without reference to a Purchase Order? If so, how can I do this
2.     What are the relevant movement types when GI is made w/o reference to a Purchase Order?
3.     Can GI be made with reference to any other entity/object other than PO?
Thanks

1. Can I do the Goods Issues without reference to a Purchase Order? If so, how can I do this
No u can't ..u have to do Goods receipt for a PO
Raise a PO for the same material and do GR
2. What are the relevant movement types when GI is made w/o reference to a Purchase Order?
u cant do GI for PO
3. Can GI be made with reference to any other entity/object other than PO?
GI aganist cost centre, production order, reservations ....
the easier way to bring in stock of a material is to do intial entry thru MB1C with mvt type 561.

Material Plant Level or Planning Plant Level

Hi Experts,
May i know what ever the material lying in the warehouse whether it is showing the stock at Maitnenance Plant level or Planning Plant level.
Also is it possible to keep the inventry at Maintnenace Plant level.
Please provide your valuable information.
AR

Hi Experts,
You mean to say if there is no planning Plant we cant make the inventory ? Please correct me if i am wrong.
Also i want to know is it possible to maintain the stock at Maintenance Plant level.Because we have four Maintenace Plant 8000,4000,1000 & 6000 and all four are assigned under one Planning Plant 2000. Here i want to know is it posssible to maintain the stock under all four Maintenance Plant if yes then what i have to do for the same.
AR

Can you Please Tell Me the Process for service/operation provide by one plant to other plant.

Can you Please Tell Me the Process for service/operation provide by one plant to other plant.
In My Company No Of Plants Like 1000,2000,3000,4000
Plant 1000 Provide the service/operation like (welding ,cutting, painting ) to other plants (eg 2000,3000,4000)
We want to give the profit for plant 1000 and book the service or operation charge in plant 2000 or 3000.
We don’t want to use material code in this process.
Can you help me it is possible or not through SAP PP.

Krishnendu,
Actually in my company we have one plant 1000 that plant provide the service like (CUTTING (SHAFT),WELDING,MACHINING,PAINTING)
actually plant already made one material xyz and supply 2000 plant .
we can use STO in this scenario and set special procurement key 80.
But my requirement is after some time plant 1000 provide few operation in xyz material that material already supply to 2000 plant.
in this case we dont use to produce any material.

WorkCenter/plant at Operations level vs WorkCenter/Plant @ Header level

Similar Messages

Maybe you are looking for