Skip to Content
author's profile photo Former Member
Former Member

Release Strategy @ Company Code Level

Hi Guys:

We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).

Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?

with Characteristics as Company Code ,PO Document Type and PO Value?

Thanks

Sweth

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Aug 24, 2011 at 01:17 PM

    Yes. you can set release strategy at company code level with characteristics (CEKKO_BURKS) also with DOC TYPE (CEKKO_BSART),Value (CEKKO_GNETW), Purchase Orgn (CEKKO_EKORG),Purchase Group (CEKKO_EKGRP),

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 24, 2011 at 05:31 PM

    Hi

    For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,

    The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.

    The characteristics for release strategy for external purchasing documents are

    Plant - WERKS

    Pur.group - EKGRP

    Pur.org -EKORG

    Acc.assignment category-KNTTP

    Document value-GNETW

    Document type-BSART

    The table is CEKKO

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 24, 2011 at 05:37 PM

    Hi Sweth,

    Can tell us the issue your facing ? you can set the release char based on your company code with CEKKO_BURKS.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.