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

Similar Messages

  • ESX Maintenance Standard Operating Procedures (SOPs)

    Do you use SOPs for ESX maintenance?  I'm currently compiling some for VIOPS taken from my own experience - I think I've spotted a pattern, you see...
    Also, I love the work of the IT Process Institute, Gene Kim (CTO Tripwire) and Kevin Behr (Assemblage Pointe) and others on bringing science to IT... ever heard of the Toyota Production System?  Ever heard of an IT version?  But I digress (if your interest is piqued - private message me!).
    Back to the SOP - do you have one for ESX maintenance?  My work so far has found five different triggers:
    Swap - e.g. replace failed drive
    Patch - e.g. security patch
    Upgrade - e.g. minor release like 3.5 U2
    Configure - e.g. lock down SSH so you can only access via bastion/jump box
    Observation - e.g. to run a vmsupport script
    So now I'm thinking that ESX Maintenance isn't an SOP, but a collection of SOPs - and the real SOPs are those five above.
    But what does an SOP look like?  The most basic example is a list of steps, but that's not enough for me.  I want something that brings science to IT and allows for continuous improvement.  I want the procedure to be followed rigorously, consistently - and where there is deviation it is because either (a) the process can be improved (improve the process), or (b) the person needs to be improved (improve the person - training).
    So for my gold standard of SOP I've thought of the following attributes - and each SOP should fit on one piece of A4 paper
    Trigger / Driver - what starts this whole thing, possibly a connection to a preceding SOP?
    Input - what information is required to do this job?
    RACI - for this procedure, who is Responsible (who does it), Accountable (who supervises?), Consulted (who helps), Informed (who is notified)
    Resources - what tools and suchlike are needed for the actions (e.g. the list of changes to make to /etc/ssh/sshd_config
    Actions - the unambiguous action to do, down to the most intricate detail - do not summarize, do not leave open to interpretation.
    Timing - for each action, like the marks on the Toyota production line that shows in 32s you should be at step 3.
    Output - A measurable outcome
    So I'm desperately seeking SOPs and people who are interested in this stuff - I believe it's the key to increasing throughput and reliability of change, as do many others... do you?

    I'm planning on separating a SOP from an STP - Standard Technical Procedure.
    So the SOP will have a list of actions / STPs with how long they should take... example:
    1.  On the SOP, one action is "logon to host" and it should take 2 minutes
    2.  The STP is "Use SSH + RSA keyfob to connect to bastion.vmware.com, then SSH from bastion to host with username"
    So on the A4 piece of paper, it does not go into n'th degree of the technical procedure, which may, as you say, require screen shots and stuff.
    And the A4 suggestion is figurative, because all of this should be online anyway, but keeping it short is my point.
    An SOP is equivalent to a project manager's Work Package (Prince2 term?).
    Like you say, I'll write up a sample and try and get that looking good with your help (and others?) - then tackle the rest.
    I am particularly keen on the time it takes to do an SOP... not just the steps required.  How does one limit unplanned yak shaving (to quote John Troyer!).
    Your list looks great, and I've seen a similar one in PSO with HTML interactive screens...

  • Standard Operating Procedures on SharePoint - Ideas?

    Hi folks,
    I manage operations on the business/service side of a software company. We use SharePoint lists to track a lot of "widgets" that get processed by various team members across the ops organization. These SharePoint lists function like work queues for many
    widget-processing teams.
    Can anyone shed some light on how they use SharePoint to manage and store Standard Operating Procedure (SOP) documents for processing widgets? I'm looking for ideas that go beyond the plain, simple Document Library where you simply upload a document.
    Is anyone using a SharePoint Wiki, HTML, or some other format to document business processes?
    Our organization uses Salesforce as well, and Salesforce has a pretty powerful KnowledgeBase tool, but I'd prefer to keep our processors in SharePoint since that is where most of their work lives.
    Any insight or ideas that you could provide would be great! Also, does anyone know of any SharePoint user forms that are more geared to business users rather than development?

    Hi Ethan,
    There is a 3rd party plugin tht will allow you to track reads/assigns documents called docread.
    Sounds like its what you might be looking for?
    http://www.collaboris.com/products/docread
    http://www.collaboris.com/products/docread/screencasts
    http://twitter.com/insy09 http://friendfeed.com/insy09 http://zebracube.wordpress.com

  • How to map operation subcontracting in a process order.

    Dear Gurus,
    How to map operation subcontracting in a process order.
    there are five operations in a process after three operations the material is send to a subcontract for further processing(i.e the fourth) then it comes to the plant and the fifth operations completed
    How can i map this process .
    Thanking you in advance
    Regards
    Ram

    Hi,
    have you tried external operations in  receipe.  There you need to maintain all the procurement realted data for that particular operations that is done outside,  and system creates PR for every process order that you release.  However the material goes and comes in without any material number  (as WIP).
    If you want to have more control,  create a part number before SC operations  and afer SCoperations   and then use subcontracting process in procurement. 
    The need determines which option you can go with.
    cheers
    Rav

  • How is Standard Operation attachments copied to Work Order (Jobs)?

    It seems the Job is linked to the Standard Op attachment, and as the Standard Op attachment is changed, it changes the attachement for previously Closed Jobs.
    Is there a way to copy the attachement at the time of Work Order creation?

    yes

  • Standard Operating Procedure For Cisco Firewall

    Hi,
    i want to ask it is cisco have a SOP about Firewall because i want to create SOP for my company.

    My post above includes a link at the word "here". Sometimes thay can be hard to see in the posts. Here's the link:
         http://www.cisco.com/en/US/netsol/ns982/networking_solutions_program_home.html#~bng

  • Database Standard Operating Procedures documentation

    Hi,
    I'm looking to standarised Oracle Database processess including planning,configuration,Installation, maintenace etc. by using best practices. Please advice where I can find best practices docu and other standared.
    thanks

    I would start by looking at Oracle's support and technology network. There are often white papers and similar written about best practices for different features of Oracle.
    http://www.oracle.com/technetwork/index.html
    or particular for databases
    http://www.oracle.com/technetwork/database/features/index-152657.html
    finally i go to the search page and type in best practices ???? for what every i want to see best practices on.
    http://search.oracle.com/search/search
    Here is a very small presentation that I found by googling.
    http://www.virtual-dba.com/pdfs/Xtivia_WP_Oracle_Best_Practices_2008.pdf

  • Editing of scheduled dates in Process Order Operations

    Hello,
    I have a requirement, in which the client would like to change the Scheduled dates in the operation details of a process order.
    In the header screen of a process order, if we change the basic start / finish dates (depending on forward or backward scheduling), and reschedule the process order, the process order is rescheduled, with the new dates.
    The client's requirement is, they should be able to change the Scheduled dates in the tab "Operation - Dates", of the "Operation overview" screen, in a process order. Normally the field is not editable, and the system calculates the dates, based on the start / finish dates, entered in the process order header.
    I would like to know, what is the way out, to meet this requirement.
    Thanks.

    Hi,
    As every body else is explaining it is not possible for standard SAP ,  as of normal business or any business scenario why would a client want to change the operation dates from Production order ( still not understood.....)
    There are two options to do that:
    1) Copy the whole transaction ( programmes ) into some Z - transaction and in the programme you can change the object ( CO_VG_OPR_*) from being grayed out.
    This will alllow you to change the dates.
    2) you can go for enhancement with the following FM
        BAPI_ALM_ORDER_MAINTAIN
    I suggest you to clear these things with client.These things require more of ABAP work.
    And as said changing the standard behaviour of the system can cause performance issues.
    Please close the thread if satisfied.
    prakash

  • Operation does not fetch in process order

    hi PP-Pi gru,
    when i am creating process order from planed order , operation ( master recipe) does not fetch in process order..only take default operation 10, kindly suggest me how all operation will fetch in process order
    another mater is when assign production profile  in  t- code CORU show the error massage  " production scheduling profile for plant ALIV,order type does not exist"...but we have used stander order type PI01..kindly suggest me
    Rogers
    Aqueel

    Hi,
    Check In master Recipe ,in the PI Tab,There must be some PI category is assigned and in that PI Category,this PI Charactiristic has been assigned.
    First goto that Phase of the Master Recipe and then goto PI tab and then find the PI category.
    You need to define production scheduling profile for your plant in OPKP which is assign to order type dependent parameter  COR4 In planning screen. Please check. Also check the work scheduling view of material master.
    Regards,
    R.Brahmankar

  • Deleting operations in master recipe of process orders

    Dear Guru's,
           I want to delete the operations in master recipe of process orders. The operation numbers are different in different process orders. This activity has to be performed on bit large number of process orders. Can anyone help me in providing the process for doing this activity in mass. Any suggestions?
    Thanks in advance.
    Regards
    Kalyan

    Dear Kalyan,
    Why do you want to delete the operations(basically phases)at process order level?
    If it's really required to execute the Shop floor activties and if the order numbers is huge in number means then in my
    understanding only a LSMW/BDC can help you,but technically I'm concerned about selecting the operation/phases for deletion
    by passing on the confirmation number or operation number for a particular process order.
    If it would be the latest operation/phase for a product means then make the changes in the master recipe so that the same is
    getting copied into the process orders in the future.
    Check and correct me if I'm wrong.
    Regards
    Mangalraj.S

  • 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 ?

  • Process order IDOC

    Hi Gurus,
    Please help.
    I wanted to send "All" details of a process order to a legacy system "immediate". All details includes process order header material, operations, all components and their details.
    In material master (master data) we can activate change pointer for material and use BD21 to schedule (every xy minutes) to send the material master to a remote system.
    Do we have such facility in process order (production order)?
    I did the research on following:
    POIT : Good transaction but unable to get the process orders which are changed for a given time
    LOIPRO: Used this mesage, but it is not selecting all components of a process order
    Is there a "standard way" to trigger the process order details to a legacy system?
    Thanks for your help.
    - Nagarajan

    Hi,
    Thanks for your reply. My requirement is to send the process orders during each save time after the process order is released. Before release is also fine, so in general the requirement is send the process order to a legacy system whenever the process order is saved.
    I tried to execute this program with material number range, logical system and message type "LOIPRO". It didn't do anything.
    Please help.
    Thanks
    Nagarajan

  • Subcontractin by process order: ME2O

    Hello everybody,
    I’m implementing subcontracting by process order.
    I feel very unsuitable with the transaction ME2O that we use to post GI to the vendor.
    The problem is that we need insert the code of every components that we send.
    As an alternative, we can insert just the vendor, but in this case we get a lot of material in output.
    The problem is overall that, if we send material managed to batch, we need insert the batch number.
    All this is very bad because add a lot of steps to the operator job.
    Is there the way to get in ME2O with the process order number or simplify any step?
    Best regards,

    Dear,
    There are two ways of subcontracting in SAP...opration subcontarcting and material sub contract
    <b>Operation sub contract in process order</b> -  Tick the sub-contracting box in Routing. This will not create Subcontracting PR during MRP run. This will create PR during Production order release or that particular operation is released.
    - In the above case, after the first operation if you are sending it to contractor then there will be any entry in Inventory management as it is not material subcontracting it is only SERVICE subcontracting i.e. this particular operation is subcontracted. This procedure is followed when contactor is working with in your company premises.
    <b>Material sub contract</b> - The procedure you are talking about the <b>material subcontract...</b>the procedure is as below
    Let us say you have a final product C.
    C needs B
    B need s A
    A needs raw material X and Y
    In the above case
    C and B is having routing
    In A material master MRP2 view....enter special procurement key as subcontacting(in STD sap the key is 30), procurement key = F
    A has a BOM having items X and Y.No routing for A
    When youn run MRP
    System will create Pl order for C and B, SUBCONTACTING PR to A and PR to x and Y
    After you procure X and Y, You can convert PR of A to PO.
    Then you will send the material i.e. issue the material to subcontractor through 541 and special stock O.
    This stock you case see in MMBE with special stock O.
    Once you receive the material A, when you do GR, the materials are issued to A and A will be inventarised with mov type 101.
    The cost of serve and the cost of raw material is booked to cost center entered in subcontracting PO.
    The cost of this will be settled to production order later.
    I hope it is clear.

  • Process Order cannot be reversed

    Hi PP Gurus,
    When reversing process order for confirmed scrap quantity using tcode CORS.
    System will prompt an error message. Please advice if confirmed operation scrap quantity
    for process order can be reverse?
    Thanks,
    Sodacracker
    Edited by: sodacracker on Jul 7, 2010 12:44 AM
    Edited by: sodacracker on Jul 7, 2010 1:11 AM

    Dear
    Confirmation Reversal through CORS - is cancellation .If the process order was designed for Backflushing and Auto GR, then the reversal of all goods movment also happens when canelling confirmation.
    But what sort of erro mesge are you getting ? Are u getting any period issue or scrap reversal ? Did u try in MBST ?
    Come back with exct error messeg for farther analysis
    Regards
    JH

  • Process Order Details like batch number, mfg date flow to a new process ord

    Hi Experts,
    I have a doubt in Process Order.
    I have two stage production.
    1. Blending
    2. Packing
    I create a process order for blending and assign a batch number and manufacturing date for Blending operation.
    Release the process order.
    Final Confirmation of the process order.
    I complete all the process, Goods Reciept is done.
    Technically completed the Process Order.
    Now my 1st stage Process order is completed and ready for the 2nd stage production i.e., Packing.
    Now I create a new process order,
    here I am having the problem that I need to enter all the details like batch number, manufacturing date etc..
    I want to avoid this in the 2nd process order.
    How to do this i.e., carry forwarding the details of the 1st process order into the 2nd process order.
    Is there any setting required at the back end?
    I was told about Push operation to rectify the above problem. But I am not clear about that.
    Can any one clearly explain about that step- by - step.
    Thanks in advance,
    Regards,
    B. Praveen
    Praveen

    closing thread

Maybe you are looking for