Additional standard text in Process order

Hi gurus
I have a question. I have maintained a standard text in RECEIPE and the same gets copied into process order. In the process addionally i have added a standard text to an exting phase. But while printing the shop floor papers , the same is not getting printed. Only the one attached in the receipe is getting printed. Can anyone help he with this?
I need both to be printed in the SFP
Prasanna

solved

Similar Messages

Long Text in Process Order

Hi ,
I want to add the long text in Process Order screen.
I had seen the long text tab is in the production order screen(CO01) but i could not find the same in the process order screen(COR1). Is there any customization or any user exit required to add the long text in the process order screen.
Thanks & Regards,
Jish.

Hi
Suzie
U will find the (Create Long text ) in the header of the Process order, NEAR Process order number and Header Material.
Reg
Madhu

Goods Receipt for Material which has no Standard Price in Process Order

Hello everyone, is there a way by which we can prevent GR for process order which contains material that does not have standard price? And if ever we received material using process order how can we correct the process order right after we correct the standard price.

Hi,
i just don't know why you raised new thread as already ur previous thread is not closed
Now just let us know whether system is throwing any error
or what exactly happing in cofirmation screen
Go to OPK4, here
under goods movement there is option all components just tick it
then in second tab Gen individual entry tick Goods movement & termination for incorrect goods movement
Coming to GR
what is storage location ur giving
just check in MMSC, whether this storage location is activated for the header material ( GR )
Added
Plz Go through all possible options
[Auto GR is not happening.;
Regards
kumar
Edited by: kumar kumar on Nov 10, 2009 2:25 PM

Standard Text Key in order

Hi
I created std text key in CA10
How to configure in "Assign standard texts for short messages to order types" ?
Alagesan

The standard text key created by using CA10 will reflect against maintenance order in operation tab when selected from standard text key field in maintenance order operation tab.
For the above said function no configuration is required. what every standard text key is selected for first operation, is copied automatically in maintenance order short message (provided that short message is not given by user different then first operation).
Hope this reply helps you.

Standard Text SO10-Purchase Order

Hi,
The requirement is like this;
I have maintained a standard text in Transaction SO10.
When i create Purchase order first time, it takes the standard text that i have maintained in SO10 when i see the preview. But then if i go to change mode of Purchase order & change/input the header text in Purchase Conditions.After saving it overwrites the standard text & takes the text that i put in Header Text in Purchase condition.
Now my requirement is even i change the header text of Purchase Condition, it should always take Standard Text that i have maintained in SO10. How i can control this, is there any user exit etc which can help.
Appreciate your support in this regard.

why do you delete the standard text in the PO while extending this text?

Global Standard for TECOing Process Orders

Hi All,
Is there any standard rule for how long it should take for a process order to be TECO'ed?
Currently our PO's get TECO'ed anywhere between 2-8 days after confirmation. But we do have them all TECO'ed prior to month end. I would prefer to set a general rule (based on global and benchmarking standards) on how many days it should take us to TECO them.
Appreciate your help and inputs.
Thanks,
Deeksha

Dear Deeksha,
Once the process order has been confirmed with final confirmation or say the complete confirmation,goods movements(Gi&Gr)
activities are completed,then the TECO status can be set on the same day of final confirmation and GR or else on the next day.
If my understanding is correct then SAP suggests to set the TECO status once the shop floor activities are completed and no
where I could see the no of days for performing this activity.
If required this can be individually set at process order level in COR2 or else as month ending activity by setting TECO for a list
of process orders using T.Code COHVPI.
Check and revert back.
Regards
Mangalraj.S

Standard costing in Process order for external operation

Hi SAP - PP gurus,
Need your expert suggestion on the current scenario. We are having a sequence of operations in a process order. One specific operation is used to trigger subcontracting activity for completion of some services.
while calculating the total planned & actual costs & variance costs for the process order as a whole , we are not getting the desired results.
The planned cost is not getting calculated or variance is not populated correctly. what might be the problem or is there any alternate solution to approaching this scenario.

I do not have an 'expert' response for you - but I can share my experience and maybe both of us will learn the 'truth' before too long.
In the external processing - indicator in the control key for a phase/operation in a recipe - when it is set, the system requires that either a Purchasing Information Record or an Outline Agreement # and Outline Agreement line item # be entered. If I enter a PIR, the data from the PIR is loaded into the external op fully. This results in a proper cost roll-up and proper processing.
If I use an Outline Agreement + Item # - the system expects me to copy all this detailed information into the remaining General Data fields (that were populated automatically when I used the PIR). I don't have to enter anything except the OA + Item numbers. But if I do not enter a price - then I, like you, get less than acceptable pricing because this operation is NOT priced (I do get a warning - this leads me to believe that SAP will not be populating these fields - the warning is to remind ME to do it --- I want the system to do it since I am specifying the OA + item numbers).
I have searched help and now have posted an OSS note for the answer to this: The PIR does what I want (it has to be created prior to application of course), but because External processing is merely a service and can't be specified by Material # and it only works per Material Group # - then I only have the chance to enter one price per Material Group - and that is insufficient in my situation (I have about 50 materials per each group and each item can have a different price). So I have to use OAs - and not having them able to trigger auto copying into the external op phase - this causes a lot of extra work and risk of data inaccuracy (mis-keying the price, etc.). There does not seem to be a fix - so I think the manual application in the ext op will be your recourse.
Let me know if you have learned more.

Long Text problem in Process order header

Hi All,
I am using SAVE_TEXT FM to update the header long text in process order.
Also, I am updating the field AUFK-LTEXT = 'E'.
But when i display the order and click on long text, it does not display any thing as the text is not saved.
When I update the text directly in the order using COR2, it gets saved.
Does anyone know why the text is not being saved through FM SAVE_TEXT?
Also tried COMMIT WORK but was not successful.
The paramters I am passing to the FM are
TDOBJECT = 'AUFK'
TDID = 'KOPF'
TDSPRAS = SY-LANGU
TDNAME = sy-mandt+order number with leading zeros.
and the text lines in internal table.
Am I missing anything else here?
Thanks,
Sandeep

Hi Sandeep,
First check table STXH for the order which you saved manually, in order to verify that the values you are passing to the FM SAVE_TEXT are correct.
Also check the documentation which is supplied with this function to determine the INSERT and SAVEMODE_DIRECT values.
Also maybe check function COMMIT_TEXT and its documentation.
Regards,
Robert
PS. also test the scenario in which text s/b added to already existing text. The SAVE_TEXT function wipes out everything and therefore you first should read the existing text (READ_TEXT) to retrieve the current text and save this together with the new text using SAVE_TEXT. (check function group STXD for possible related functions to use).
PPS. Thinking about my comments under PS., I recall now that this was the symptom of the long text passed on through BAPI_SALESORDER_CHANGE and therefore maybe this is not the case for SAVE_TEXT.
Edited by: RJ. Schamhart on Feb 3, 2011 4:53 PM

Default Standard Text Key or Standard Text to first Operation of Order

I would like to have a standard text key or standard text defaulted for the first operation of an order created via IW31 of certain order type.
For example we have an order type called CORR for corrective orders. When ever there is a break fix, the user would create a CORR order via IW31. When this order type is used I want the first operation to have a predefined Standard text key defaulted. In this case we was our first operation to have a safety message and precautions listed.
This would work similar to a planned order that calls from a task list and has text in the task list.
I did some review and testing of the "Assign Standard Texts for Short Messages to Order Types", but as I understand it, this only works for sending message and not including text on the operation.
Is what I want to do possible? Or would it make more sense to use an exit like IWO10020, Maintenance order: Automatically include task list . I guess I could create a general task list and use that in this exit for all CORR order types.
Edited by: Darrell Dorsey on May 25, 2010 10:26 AM
Edited by: Darrell Dorsey on May 25, 2010 10:30 AM

For the scenario that you are referring to, i believe this would be the option that would be flexible. Yes, you will have to little bit of custom development for this and i don't see any standard functionality to default the standard text on the first operation for specific order types. You should be able to attach a task list where its planning plant differs with that of the Order plant.
There are much more simpler options available, if you are open to using a different work center(You could default the Standard text key on the work center), if you are open to create a separate transaction for this order type (you could default the Standard text by creating a transaction variant through SHDO), If you are using GuiXT widely in your organization you could write a small simple script to default the Standard text for this order type.
Regards
Narasimhan

Sapscript Standard Text Printing - Format Problem

Heros,
I wanted to print one standard text(Basic Text of Process order) in sapscript.I am using the INCLUDE command instead of Read_text FM , so that I can keep the Paragraphs of that text intact.But I am falling short of two requirements of my client.
1. He has highlighted Some words of the text and underlined some of the text. He wants that character format intact in spascript.How can I do that?
2. The script initaly was using Read_Text and was storing the value in a variable wa_line and was printing in script as
[LI ] DESCRIPTION: &wa_line&
so it was printing like
DESCRIPTION: fasfoihfaishfiahfiafhfihfahfiashfiahfahfiafiasfihahfisahfafasi
But now I am using INCLUDE command as follows
[LI] DESCRIPTION:
[: /] INCLUDE OBJECT BLAH BLAH
So it is printing like
DESCRIPTION:
fasfoihf
aishfiahfiafhfihfa
hfiashfiahfa
hfiafiasfihahfisahfafasi
I want to get them in same line.
I mean
DESCRIPTION: fasfoihf
aishfiahfiafhfihfa
hfiashfiahfa
hfiafiasfihahfisahfafasi
Is that possible?
Reward Point Guranteed.

Hi Anid,
When you are creating your standard text the default value in the tag column is *. If you change this value to = (Extended line) the display of standard text will start in the same line as the previous value (in your case it will display the standard text in the same line as DESCRIPTION:).
Hope this solves your problem!
Regards,
Saurabh

Progress confirmation for process order

Hello to all,
I want to use the progress confirmation functionality for process order. I know that it is possible for production orders, but I couldn't find respective transaction for process order. Do you know if it is possible to use progress confirmation for process orders.
BR,
Nikolay

Thanks for your inputs, but they are not useful!
COR6 - it cannot be used once the order is confirmed at phase level;
COOISPI - it's a report
COR6N -it is the standard transaction for process order confirmation
I want to do so-called "unplanned milestone" for process orders, something similar to CO1F for production orders.
BR,
Nikolay

Why no freight record exist in OE_PRICE_ADJUSTMENTS after process order api

Hi experts,
I have this procedure to call process order api to copy exist line then create line and also copy existing freight charges and create freight charges. But, the procedure only can create new line, but i can't see the freight charge to be created in OE_PRICE_ADJUSTMENT.
can anyone advice what's wrong in my coding? I have Lygine my changes.
Regards,
Lygine
PROCEDURE create_line
    p_header_id            IN NUMBER,
    p_old_line_id          IN NUMBER,
    p_qty                  IN NUMBER,
    p_item                 IN VARCHAR2,
    p_inventory_item_id    IN NUMBER,
    p_organization_id      IN NUMBER, -- 51305
    p_subinventory         IN VARCHAR2,
    p_schedule_date        IN DATE,
    p_freight_carrier_code IN VARCHAR2,
    p_shipping_method_code IN VARCHAR2,
    p_freight_terms_code   IN VARCHAR2,
    p_new_line_id          OUT NUMBER,
    p_new_order_line       OUT VARCHAR2,
    p_return_code          OUT NUMBER,
    p_return_message       OUT VARCHAR2
) IS
    l_pkg VARCHAR2(60) := 'seaoe_partsub.create_line';
    l_opn VARCHAR2(10) := 'Create';
    l_stmt VARCHAR2(500);
    l_org_id       NUMBER := fnd_global.org_id;
    l_user_id      NUMBER := nvl(fnd_global.user_id, -1);
    l_resp_id      NUMBER := nvl(fnd_global.resp_id, 21623);
    l_resp_appl_id NUMBER := nvl(fnd_global.resp_appl_id, 660);
    -- Variables for process order API
    l_header_rec     oe_order_pub.header_rec_type;
    l_line_tbl       oe_order_pub.line_tbl_type;
    l_action_request oe_order_pub.request_tbl_type;
    l_return_status VARCHAR2(50);
    l_msg_count     NUMBER;
    l_msg_data      VARCHAR2(5000);
    l_msg_index_out NUMBER;
    l_result        VARCHAR2(2000); -- Added 06-Dec-2005
    l_short_msg VARCHAR2(250); --limit l_err_msg to size 250
    p_api_version_number NUMBER := 1.0;
    p_init_msg_list      VARCHAR2(10) := fnd_api.g_false;
    p_return_values      VARCHAR2(10) := fnd_api.g_false;
    p_action_commit      VARCHAR2(10) := fnd_api.g_false;
    p_action_request_tbl oe_order_pub.request_tbl_type;
    x_return_status          VARCHAR2(1);
    x_msg_count              NUMBER;
    x_msg_data               VARCHAR2(100);
    x_header_val_rec         oe_order_pub.header_val_rec_type;
    x_header_adj_tbl         oe_order_pub.header_adj_tbl_type;
    x_header_adj_val_tbl     oe_order_pub.header_adj_val_tbl_type;
    x_header_price_att_tbl   oe_order_pub.header_price_att_tbl_type;
    x_header_adj_att_tbl     oe_order_pub.header_adj_att_tbl_type;
    x_header_adj_assoc_tbl   oe_order_pub.header_adj_assoc_tbl_type;
    x_header_scredit_tbl     oe_order_pub.header_scredit_tbl_type;
    x_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type;
    x_line_tbl               oe_order_pub.line_tbl_type;
    x_line_val_tbl           oe_order_pub.line_val_tbl_type;
    x_line_adj_tbl           oe_order_pub.line_adj_tbl_type;
    x_line_adj_val_tbl       oe_order_pub.line_adj_val_tbl_type;
    x_line_price_att_tbl     oe_order_pub.line_price_att_tbl_type;
    x_line_adj_att_tbl       oe_order_pub.line_adj_att_tbl_type;
    x_line_adj_assoc_tbl     oe_order_pub.line_adj_assoc_tbl_type;
    x_line_scredit_tbl       oe_order_pub.line_scredit_tbl_type;
    x_line_scredit_val_tbl   oe_order_pub.line_scredit_val_tbl_type;
    x_lot_serial_tbl         oe_order_pub.lot_serial_tbl_type;
    x_lot_serial_val_tbl     oe_order_pub.lot_serial_val_tbl_type;
    -- Cursor to get old line
    --Add all Attribute, Industry_Attribute and TP_Attribute,Rex, 15JUL2010
    CURSOR line_cur IS
      SELECT invoice_to_org_id,
             price_list_id,
             payment_term_id,
             ship_to_org_id,
             sold_to_org_id,
             attribute1,
             attribute2,
             attribute3,
             attribute4,
             attribute5,
             attribute6,
             attribute7,
             attribute8,
             attribute9,
             attribute10,
             attribute11,
             attribute12,
             attribute13,
             attribute14,
             attribute15,
             attribute16,
             attribute17,
             attribute18,
             attribute19,
             attribute20,
             fob_point_code,
             freight_carrier_code,
             freight_terms_code,
             line_type_id,
             order_quantity_uom,
             org_id,
             orig_sys_document_ref,
             orig_sys_line_ref,
             pricing_quantity_uom,
             request_date,
             shipping_method_code,
             ship_from_org_id,
             sold_from_org_id,
             tax_code,
             tax_date,
             tax_exempt_flag,
             tax_exempt_number,
             tax_exempt_reason_code,
             unit_list_price,
             unit_selling_price,
             shipping_instructions,
             packing_instructions,
             calculate_price_flag,
             industry_attribute1,
             industry_attribute2,
             industry_attribute3,
             industry_attribute4,
             industry_attribute5,
             industry_attribute6,
             industry_attribute7,
             industry_attribute8,
             industry_attribute9,
             industry_attribute10,
             industry_attribute11,
             industry_attribute12,
             industry_attribute13,
             industry_attribute14,
             industry_attribute15,
             industry_attribute16,
             industry_attribute17,
             industry_attribute18,
             industry_attribute19,
             industry_attribute20,
             industry_attribute21,
             industry_attribute22,
             industry_attribute23,
             industry_attribute24,
             industry_attribute25,
             industry_attribute26,
             industry_attribute27,
             industry_attribute28,
             industry_attribute29,
             industry_attribute30,
             tp_attribute1,
             tp_attribute2,
             tp_attribute3,
             tp_attribute4,
             tp_attribute5,
             tp_attribute6,
             tp_attribute7,
             tp_attribute8,
             tp_attribute9,
             tp_attribute10,
             tp_attribute11,
             tp_attribute12,
             tp_attribute13,
             tp_attribute14,
             tp_attribute15,
             customer_line_number,
             shipment_priority_code
        FROM oe_order_lines_all
       WHERE line_id = p_old_line_id;
    -- Start Added on 06-Dec-2005
    CURSOR hold_cur
      cp_header_id NUMBER,
      cp_line_id   NUMBER
    ) IS
      SELECT ohd.hold_id
        FROM oe_hold_definitions ohd,
             oe_hold_sources_all ohs,
             oe_order_holds_all ooh
       WHERE ooh.header_id = cp_header_id
         AND nvl(ooh.line_id, -1) = nvl(cp_line_id, -1)
         AND ooh.hold_source_id = ohs.hold_source_id
         AND ohs.hold_id = ohd.hold_id
         AND ooh.released_flag = 'N'
         AND ohd.hold_id != seaoe_defaults_pkg.get_wait_for_cms_hold;
    -- End Added on 06-Dec-2005
     CURSOR warranty_cur IS -- Lygine 09-Dec-2011
       SELECT list_header_id, list_line_id,
             list_line_type_code, change_reason_code, change_reason_text, operand,
             arithmetic_operator, modifier_level_code, charge_type_code, context,
             attribute1,attribute2,attribute3,attribute4,attribute5,attribute6,attribute7,attribute8,attribute9
      FROM OE_PRICE_ADJUSTMENTS
      WHERE list_line_type_code = 'FREIGHT_CHARGE'
      AND   automatic_flag = 'N'
      AND   line_id = p_old_line_id
      AND   header_id = p_header_id;
      l_line_adj_tbl oe_order_pub.line_adj_tbl_type; -- Lygine 09-Dec-2011
BEGIN
    p_return_code    := 0; -- 0 is success --1 is fail
    p_return_message := 'Entered create_line sub proc.';
    -- FND application initializes --
    -- Varariables for FND_GLOBAL.APPS_INITIALIZE
    -- Assign 11i id to the variables in order to
    -- Get_Order_Number when process order API if
    -- script is running from SQL prompt.
    -- Note:
    -- If running from SQL prompt without submitting via concurrent program,
    -- cannot use FND_GLOBAL.USER_ID,FND_GLOBAL.RESP_ID and FND_GLOBAL.RESP_APPL_ID
    -- these function return -1 which is not able to get Sequence Number profile setting.
    -- Thus, these values are pass-in as parameters
    fnd_client_info.set_org_context(l_org_id);
    fnd_global.apps_initialize(user_id      => l_user_id,
                               resp_id      => l_resp_id,
                               resp_appl_id => l_resp_appl_id);
    -- Initialization --
    oe_msg_pub.initialize;
    oe_debug_pub.initialize;
    l_header_rec := oe_order_pub.g_miss_header_rec;
    l_line_tbl(1) := oe_order_pub.g_miss_line_rec;
    *l_line_adj_tbl(1):= oe_order_pub.g_miss_line_adj_rec; -- Lygine 09-Dec-2011*
    -- Populate line table --
    FOR line_rec IN line_cur
    LOOP
      l_line_tbl(1).header_id := p_header_id;
      l_line_tbl(1).inventory_item_id := p_inventory_item_id;
      l_line_tbl(1).invoice_to_org_id := line_rec.invoice_to_org_id;
      l_line_tbl(1).price_list_id := line_rec.price_list_id;
      l_line_tbl(1).payment_term_id := line_rec.payment_term_id;
      l_line_tbl(1).schedule_ship_date := p_schedule_date;
      l_line_tbl(1).ship_to_org_id := line_rec.ship_to_org_id;
      l_line_tbl(1).sold_to_org_id := line_rec.sold_to_org_id;
      l_line_tbl(1).attribute1 := line_rec.attribute1;
      l_line_tbl(1).attribute10 := line_rec.attribute10;
      l_line_tbl(1).attribute11 := line_rec.attribute11;
      l_line_tbl(1).attribute12 := NULL;
      l_line_tbl(1).attribute13 := NULL;
      l_line_tbl(1).attribute14 := NULL;
      l_line_tbl(1).attribute15 := line_rec.attribute15;
      l_line_tbl(1).attribute2 := line_rec.attribute2;
      l_line_tbl(1).attribute3 := line_rec.attribute3;
      l_line_tbl(1).attribute4 := line_rec.attribute4;
      l_line_tbl(1).attribute5 := line_rec.attribute5;
      l_line_tbl(1).attribute6 := line_rec.attribute6;
      l_line_tbl(1).attribute7 := line_rec.attribute7;
      l_line_tbl(1).attribute8 := line_rec.attribute8;
      l_line_tbl(1).attribute9 := line_rec.attribute9;
      --Add the left Attribute16..20 by Rex, 15Jul2010
      l_line_tbl(1).attribute16 := line_rec.attribute16;
      l_line_tbl(1).attribute17 := line_rec.attribute17;
      l_line_tbl(1).attribute18 := line_rec.attribute18;
      l_line_tbl(1).attribute19 := line_rec.attribute19;
      l_line_tbl(1).attribute20 := line_rec.attribute20;
      --Add Industry_Attribute and TP_Attribute By Rex, 15JUL2010
      l_line_tbl(1).industry_attribute1 := line_rec.industry_attribute1;
      l_line_tbl(1).industry_attribute2 := line_rec.industry_attribute2;
      l_line_tbl(1).industry_attribute3 := line_rec.industry_attribute3;
      l_line_tbl(1).industry_attribute4 := line_rec.industry_attribute4;
      l_line_tbl(1).industry_attribute6 := line_rec.industry_attribute5;
      l_line_tbl(1).industry_attribute6 := line_rec.industry_attribute6;
      l_line_tbl(1).industry_attribute7 := line_rec.industry_attribute7;
      l_line_tbl(1).industry_attribute8 := line_rec.industry_attribute8;
      l_line_tbl(1).industry_attribute9 := line_rec.industry_attribute9;
      l_line_tbl(1).industry_attribute10 := line_rec.industry_attribute10;
      l_line_tbl(1).industry_attribute11 := line_rec.industry_attribute11;
      l_line_tbl(1).industry_attribute12 := line_rec.industry_attribute12;
      l_line_tbl(1).industry_attribute13 := line_rec.industry_attribute13;
      l_line_tbl(1).industry_attribute14 := line_rec.industry_attribute14;
      l_line_tbl(1).industry_attribute15 := line_rec.industry_attribute15;
      l_line_tbl(1).industry_attribute16 := line_rec.industry_attribute16;
      l_line_tbl(1).industry_attribute17 := line_rec.industry_attribute17;
      l_line_tbl(1).industry_attribute18 := line_rec.industry_attribute18;
      l_line_tbl(1).industry_attribute19 := line_rec.industry_attribute19;
      l_line_tbl(1).industry_attribute20 := line_rec.industry_attribute20;
      l_line_tbl(1).industry_attribute21 := line_rec.industry_attribute21;
      l_line_tbl(1).industry_attribute22 := line_rec.industry_attribute22;
      l_line_tbl(1).industry_attribute23 := line_rec.industry_attribute23;
      l_line_tbl(1).industry_attribute24 := line_rec.industry_attribute24;
      l_line_tbl(1).industry_attribute25 := line_rec.industry_attribute25;
      l_line_tbl(1).industry_attribute26 := line_rec.industry_attribute26;
      l_line_tbl(1).industry_attribute27 := line_rec.industry_attribute27;
      l_line_tbl(1).industry_attribute28 := line_rec.industry_attribute28;
      l_line_tbl(1).industry_attribute29 := line_rec.industry_attribute29;
      l_line_tbl(1).industry_attribute30 := line_rec.industry_attribute30;
      l_line_tbl(1).tp_attribute1 := line_rec.tp_attribute1;
      l_line_tbl(1).tp_attribute2 := line_rec.tp_attribute2;
      l_line_tbl(1).tp_attribute3 := line_rec.tp_attribute3;
      l_line_tbl(1).tp_attribute4 := line_rec.tp_attribute4;
      l_line_tbl(1).tp_attribute5 := line_rec.tp_attribute5;
      l_line_tbl(1).tp_attribute6 := line_rec.tp_attribute6;
      l_line_tbl(1).tp_attribute7 := line_rec.tp_attribute7;
      l_line_tbl(1).tp_attribute8 := line_rec.tp_attribute8;
      l_line_tbl(1).tp_attribute9 := line_rec.tp_attribute9;
      l_line_tbl(1).tp_attribute10 := line_rec.tp_attribute10;
      l_line_tbl(1).tp_attribute11 := line_rec.tp_attribute11;
      l_line_tbl(1).tp_attribute12 := line_rec.tp_attribute12;
      l_line_tbl(1).tp_attribute13 := line_rec.tp_attribute13;
      l_line_tbl(1).tp_attribute14 := line_rec.tp_attribute14;
      l_line_tbl(1).tp_attribute15 := line_rec.tp_attribute15;
      l_line_tbl(1).customer_line_number := line_rec.customer_line_number;
      l_line_tbl(1).global_attribute2 := p_old_line_id;
      l_line_tbl(1).cancelled_flag := 'N';
      l_line_tbl(1).created_by := l_user_id;
      l_line_tbl(1).creation_date := SYSDATE;
      l_line_tbl(1).last_updated_by := l_user_id;
      l_line_tbl(1).last_update_date := SYSDATE;
      l_line_tbl(1).fob_point_code := line_rec.fob_point_code;
      l_line_tbl(1).freight_carrier_code := nvl(p_freight_carrier_code,
                                                line_rec.freight_carrier_code);
      l_line_tbl(1).freight_terms_code := nvl(p_freight_terms_code,
                                              line_rec.freight_terms_code);
      l_line_tbl(1).ordered_item := p_item;
      l_line_tbl(1).line_type_id := line_rec.line_type_id;
      l_line_tbl(1).open_flag := 'Y';
      l_line_tbl(1).ordered_quantity := p_qty;
      l_line_tbl(1).order_quantity_uom := line_rec.order_quantity_uom;
      l_line_tbl(1).org_id := line_rec.org_id;
      l_line_tbl(1).orig_sys_document_ref := line_rec.orig_sys_document_ref;
      l_line_tbl(1).orig_sys_line_ref := line_rec.orig_sys_line_ref;
      l_line_tbl(1).pricing_quantity := p_qty;
      l_line_tbl(1).pricing_quantity_uom := line_rec.pricing_quantity_uom;
      l_line_tbl(1).request_date := line_rec.request_date;
      l_line_tbl(1).shipping_method_code := nvl(p_shipping_method_code,
                                                line_rec.shipping_method_code);
      --        l_line_tbl(1).ship_from_org_id          := line_rec.ship_from_org_id; -- 51305
      l_line_tbl(1).ship_from_org_id := p_organization_id; -- 51305
      l_line_tbl(1).sold_from_org_id := line_rec.sold_from_org_id;
      --commented for OF-OMAS TD#474 Part Substitution GST Tax, 4 Aug 2008 - Rex Qian
      --l_line_tbl(1).tax_code                  := line_rec.tax_code;
      --l_line_tbl(1).tax_date                  := line_rec.tax_date;
      --l_line_tbl(1).tax_exempt_flag         := line_rec.tax_exempt_flag;
      --l_line_tbl(1).tax_exempt_number         := line_rec.tax_exempt_number;
      --l_line_tbl(1).tax_exempt_reason_code := line_rec.tax_exempt_reason_code;
      l_line_tbl(1).unit_list_price := line_rec.unit_list_price;
      l_line_tbl(1).unit_selling_price := line_rec.unit_selling_price;
      l_line_tbl(1).shipping_instructions := line_rec.shipping_instructions;
      l_line_tbl(1).packing_instructions := line_rec.packing_instructions;
      --        l_line_tbl(1).calculate_price_flag := line_rec.calculate_price_flag;
      l_line_tbl(1).calculate_price_flag := 'N'; -- Added 06-Dec-2005
      l_line_tbl(1).subinventory := p_subinventory;
      l_line_tbl(1).operation := oe_globals.g_opr_create;
      l_line_tbl(1).shipment_priority_code := line_rec.shipment_priority_code;
    END LOOP; --for line_cur
    -- Lygine 09-Dec-2011
    -- Populate Extended Warranty Charge Line--
    *FOR warranty_rec IN warranty_cur LOOP*
      *l_line_adj_tbl(1).list_header_id := warranty_rec.list_header_id;*
      *l_line_adj_tbl(1).list_line_id := warranty_rec.list_line_id;*
      *l_line_adj_tbl(1).list_line_type_code := warranty_rec.list_line_type_code;*
      *l_line_adj_tbl(1).change_reason_code := warranty_rec.change_reason_code;*
      *l_line_adj_tbl(1).change_reason_text := warranty_rec.change_reason_text;*
      *l_line_adj_tbl(1).operand := warranty_rec.operand;*
      *l_line_adj_tbl(1).arithmetic_operator := warranty_rec.arithmetic_operator;*
      *l_line_adj_tbl(1).modifier_level_code := warranty_rec.modifier_level_code;*
      *l_line_adj_tbl(1).charge_type_code := warranty_rec.charge_type_code;*
      *l_line_adj_tbl(1).context := warranty_rec.context;*
      *l_line_adj_tbl(1).attribute1 := warranty_rec.attribute1;*
      *l_line_adj_tbl(1).attribute2 := warranty_rec.attribute2;*
      *l_line_adj_tbl(1).attribute3 := warranty_rec.attribute3;*
      *l_line_adj_tbl(1).attribute4 := warranty_rec.attribute4;*
      *l_line_adj_tbl(1).attribute5 := warranty_rec.attribute5;*
      *l_line_adj_tbl(1).attribute6 := warranty_rec.attribute6;*
      *l_line_adj_tbl(1).attribute7 := warranty_rec.attribute7;*
      *l_line_adj_tbl(1).attribute8 := warranty_rec.attribute8;*
      *l_line_adj_tbl(1).attribute9 := warranty_rec.attribute9;*
    *END LOOP; -- for warranty_cur*
    -- Call Oracle standard API to process order             --
    -- Operation: Update - ordered_quantity on original line --
    oe_order_pub.process_order(p_api_version_number => 1.0,
                               p_init_msg_list      => fnd_api.g_false,
                               p_return_values      => fnd_api.g_false,
                               p_action_commit      => fnd_api.g_false,
                               x_return_status      => l_return_status,
                               x_msg_count          => l_msg_count,
                               x_msg_data           => l_msg_data,
                               p_line_tbl           => l_line_tbl,
                               *p_line_adj_tbl       => l_line_adj_tbl, -- Lygine 09-Dec-2011*
                               p_action_request_tbl => l_action_request,
                               -- Out paramters
                               x_header_rec             => l_header_rec,
                               x_header_val_rec         => x_header_val_rec,
                               x_header_adj_tbl         => x_header_adj_tbl,
                               x_header_adj_val_tbl     => x_header_adj_val_tbl,
                               x_header_price_att_tbl   => x_header_price_att_tbl,
                               x_header_adj_att_tbl     => x_header_adj_att_tbl,
                               x_header_adj_assoc_tbl   => x_header_adj_assoc_tbl,
                               x_header_scredit_tbl     => x_header_scredit_tbl,
                               x_header_scredit_val_tbl => x_header_scredit_val_tbl,
                               x_line_tbl               => l_line_tbl,
                               x_line_val_tbl           => x_line_val_tbl,
                               *x_line_adj_tbl           => l_line_adj_tbl,*
                               x_line_adj_val_tbl       => x_line_adj_val_tbl,
                               x_line_price_att_tbl     => x_line_price_att_tbl,
                               x_line_adj_att_tbl       => x_line_adj_att_tbl,
                               x_line_adj_assoc_tbl     => x_line_adj_assoc_tbl,
                               x_line_scredit_tbl       => x_line_scredit_tbl,
                               x_line_scredit_val_tbl   => x_line_scredit_val_tbl,
                               x_lot_serial_tbl         => x_lot_serial_tbl,
                               x_lot_serial_val_tbl     => x_lot_serial_val_tbl,
                               x_action_request_tbl     => l_action_request);

Hi all,
is it need to put ...
l_line_adj_tbl(1).operation := oe_globals.g_opr_create ?

How to customize standard text in operation tab of PM order

Hi everybody,
I am Rajat.
I have question in SAP PM:
In operation tab of PM order we have standard text, rt now i m using fresh system...kindly let me know how to enter values in that so that when i take drop down i'll see those values.
Kindly reply with the path, for customization and t-code or path for master data both.
Thanks
Warm regards
Rajat

and IMG path - plant maintenance and customer service - maintenance and service processing - Assign standard texts for short message to order types
Thanks
S.N

Attaching Standard Operating Procedure (SOP) in Process Order

Hi All,
How "Standard Operating Procedure" sheet attached into each and every process order, and also we have to restrict the release of process order which doesn't have this SOP attachment? Each and every in-house material has SOP with huge characteristic & Parameter data. How come achieve this, what is the best practice/procedure? Is this maintain through PI sheet or any other procedure along with PI sheet? Please suggest.
Thanks

Hi Anupam sharma,
Thanks for your reply. Can we use the document creation (CV01N) functionality without implementing DMS? Our requirement is each and every in-house produced material having SOP sheet which is contain lot of parameters as well as having instruction (long text). We are currently maintain as an excel sheet. We have to attach each file against each material and it should be attached with PI sheet. Let us know the possibility, 2 cases we have planned to try,
1. No input parameter value, all are having static value and instruction (attached with each and every process order as an PI sheet)
2. Need to input value for some of the parameters along with some instruction steps (Long text)
How the below functionality will help us to meet the requirement?
Displaying of Documents From Document Management System - Process Management (PP-PI-PMA) - SAP Library
How to attach a file against each and every material, where these file will stored? Please suggest us with some more information
Thanks

Text in PI Sheet and Process Order did not match

Dear Sir,
We are going to upgrade to our system from 4.7 to ECC6.
We have a problem with PI Sheets with the Long text. The text instruction shown in the PI sheet is not matching with the long text put in the Process Order and Master Receipe.
We are using the Process Instruction Category "INST" and we are puting long text for instruction for this in the Master Receipe. At the time for creation of Process Order this Process instruction Category fatch correct value of long text from the Master Receipe after released the Process Order, Control Recipe generated for the same Process Order. But when we are going to process these Control Receipe from the T-Code CO60, We find the some different text for the "INST".
This problem is not for one Material and Plant Specific.
Thanks and Regards,
Gaurav Kumar
Application Consultant SAP PP
Mobile +91 9971003631

Hello Gaurav,
There might be another possibility, make sure if you make any changes in the Control Recipe Destination program or user exit to populate the long text while sending the CR to the destination to reflect with the PO/Master Recipe.
with best regards
K. Mohan Reddy

Additional standard text in Process order

Similar Messages

Maybe you are looking for