ESYU: Workbench에서 releasing을 통해 PR을 생성시 grouping 하는 방법

Purpose
Oracle Advanced Supply Chain Planning - Version: 11.5.9 to 12.1.2 - Release: 11.5
Information in this document applies to any platform.
Planner Workbench에서 Purchase Requisitions을 생성하기 위해 release 되는 line을 grouping 하는 방법에 대해 알아본다.
Solution
1. Workbenc에서 orders를 releasing 할 때, 이 functionality를 제어하기 위해 User Preferences가 setting 되어져야 한다.
ASCP: Plan/ Preferences/ Other tab에서 'Req Group By' field를 확인하고 원하는 grouping 값을 선택한다.
2. Plan Name form 안의 Production check box가 check 되어져 있는 경우 'MRP:Requisition Load Group Option'이 이용된다.
Plan Name form의 Production이 check 되어져 있으면 plan은 plan run의 마지막 부분에서 Auto-Release Planned orders를 launch 할 것이고,
profile option 값을 이 process에 의해 release 되는 line grouping을 위해 사용할 것이다.
Options 값 list는 다음과 같다:
- All on One (creates one purchase requisition for all recommended orders),
- Buyer (creates one purchase requisition for each buyer; within each requisition, creates one line for each planned order),
- Planner (creates one purchase requisition for each planner; within each requisition, creates one line for each planned order),
- Vendor (creates one purchase requisition for each vendor; within each requisition, creates one line for each planned order),
- Category (creates one purchase requisition for each item category; within each requisition, creates one line for each planned order),
- Item (creates one purchase requisition for each item; within each requisition, creates one line for each planned order),
- One each (creates a purchase requisition for each planned order) .
- Location - PO Req Import process chooses deliver to location to group the lines.
Reference
Note 779922.1

Similar Messages

  • ESYU: Planner Workbench Release process가 다른 user로부터 planned orders를 release

    Purpose
    Materials Requirement Planning - Version: 11.5.9 to 12.1
    Information in this document applies to any platform.
    11.5.9 ~ R12 version:
    두 명의 users가 MRP Planner Workbench에서 Release를 위해 records updating을 진행하는 경우, 두 명 중 한명만이 update 후 실제로 release를
    submit 했으나 두 명 user의 모든 records가 release 되어 버린다.
    User1은 자신의 Planned Orders 만을 release 할 수 있고, User2 또한 자신의 저장된 Planned Orders 만을 release 해야 한다.
    STEPS:
    1. User 1이 MRP Planned Workbench로 log
    2. User 1은 특정 planner code를 위한 current planned order recommendations 을 찾는다.
    3. User 2가 MRP Planned Workbench로 log
    4. User 2가 특정 planner code를 위한 current planned order recommendations 을 찾는다.
    5. User1은 All for Release를 선택
    6. User2도 All for Release를 선택
    7. User1은 checking process를 끝낸 후 저장
    8. User2는 아직 checking process를 끝내지 못해 save를 아지 않은 상태로 남아 있다.
    9. User1이 [Release] button을 선택
    10. User1이 [Release] button을 선택시 User1과 User2에 의해 저장되거나 check 된 모든 planned order recommendations이 Work in Process와
    Puchasing modules로 released 되어 버림
    Cause
    이 issue의 원인은 현재 MRP planning의 경우 expected functionality 이다.
    MRP Workbench Release process는 모든 planner에 의해 check 되거나 저장된 모든 planned orders를 항상 release 한다.
    Bug 891669 : Enhancement Request
    PLANNER'S WORKBENCH SHOULD RELEASE ORDERS BASED ON PLANNER NAME NOT BY BATCH
    It is explained that this is current functionality in the following rejected Enhancement Request:
    Bug 891669 : PLANNER'S WORKBENCH SHOULD RELEASE ORDERS BASED ON PLANNER NAME NOT BY BATCH
    Solution
    Solution을 적용하기 위해 아래 steps을 실행:
    1. 모든 planner에 의해 check 되거나 저장된 모든 planned orders가 [Release] button에 의해 항상 release 되는것은 현재 MRP Workbench
    Release process에서는 correct functionality 이다.
    2. ASCP Planning의 경우엔 Planner/User에 의해 Release process가 아래 option에 의해 처리 가능하다.
    -- profile MSC:Released Only By User
    -- Standard MRP에서는 이 option은 사용할 수 없고 고려되지 않는다.
    Reference
    Note 311053.1

  • Restriction of Need by Date in Planner workbench release against blanket PO

    Hi ,
    Needed some information on this query below :
    ==================================================
    For normal blanket PO, if the effective date is till 31-Jul-06 and if a release is done on this Blanket PO , with the need by date as ( example 02-Sep-06) , it still goes and does a release . There is no problem.
    But in the planner workbench release, if the need by date is greater than the BPO effective date , it does not allow to release ...
    Is this a constraint or any setup or any Profile blocking from doing this release ?
    Thanks
    Anil

    Sandeep,
    Thank yo for your information. Are you suggesting that we write an SQL report to identfy the POs which we want to update the PO Need By Date, then we utilize the Purchasing Documents Open Interface to update the PO Need By Date?
    Or would there be another way to do it from the ASCP workbench?
    We are talking about a few thousand POs ... so we need to automate.
    Thanks,
    Joe

  • Error while creating new release groups in PO release strategy

    Hi All
    I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
    But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
    Thanks for your support.
    Illan

    Dear,
    Please follow below mention path.
    *and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
    *- Follow below mention path.*
    *SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
    *Three steps involved in release process of purchase order.*
    **Edit Characteristic     Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP**
    **Edit Class     After creation of characteristic, create class for release purchase order. In which you can take reference of Class Type: - 032,Status: - Release,Class group: - Release strategy class,And put reference of your characteristic, which are created by you in first step.E.g: - Class - REL_PO**
    *Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
    Now see each steps of Define release procedure of purchase order in briefly: -
    Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    Release code     In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
    Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
    *Release Strategy     *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
    Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
    Regards,
    Mahesh Wagh

  • ECC WM Wave picking- reversal once Group is released

    We have a wave picking process, wherein a number of shipments are grouped into a wave pick Group.Group is generated
    -The transfer orders are generated from VL37 (Wave pick monitor).
    -A consolidated pick list is printed by releasing the Group.
    -The pick list is then used for the physical pick in the warehouse and transfer orders are confirmed by RF.
    The scenario is, something goes wrong after the group is released and pick list is printed.Users want to reverse/cancel the transfer orders and amend delivery.Once done, deliveries need to be assigned to a new Group, so that a fresh pick list can be printed.
    The issue in the above scenario is, once the Group is released, we are not able to dis-associate the deliveries from the Group.The error message is 'Change cannot be made due to status of reference number 103 2000000009
    Message no. VL826'
    As deliveries cannot be removed from the released Group, the deliveries cannot be assigned to a new Group.
    Is there a way to get around this?
    Thanks,
    Bikram
    Is there any way we can get around this

    Hi,
    Pls check the following SAP Notes: 492287, 539470, 1069479 and 1017834.
    It may help in your situation.
    Thanks.

  • Vendor payments release workflow!!!

    Hi all
    Can somebody explain to me how we setup standard workflow so that all vendor invoices greater than 100.000 can be blocked for payment automatically & released by some other user?
    I tried to give the document type "KR" to the workflow variant & tried to do invoicing for the vendor.  But I do not how I could release that blocked invoice...Is there any specific tcode or I have to go to the proposal & change the blocked reason from P to 'space'.
    Thanks for all your time....

    Hello Morgan,
    Payment Release Process
    Purpose
    For each workflow variant, you can specify the amount from which a payment release should be triggered.
    You can differentiate between one, two, and three-level release. This enables between one and three people to be involved in the release procedure, thus supporting both dual and triple control.
    Prerequisites
    You have made the following settings in Customizing:
    Release approval procedure
    (document type and amount for each workflow variant)
    Assign persons with release authorization
    In order to do this, you must first create release approval groups that can be entered in the customer and vendor master records.
    Depending on these criteria and the release level, you can assign release authorizations in the form of organizational objects (job, position, organizational unit) in Customizing. If you do not define any criteria (such as release approval groups), the system takes the initial value of these criteria when the payment program is run. For example, if the system was unable to determine the release approval group, the release approval procedure and the employees with release authorization are determined on the basis of release approval group zero.
    Process Flow
    Minimum requirements:
    The payment release function must be activated.
    The relevant document type must be defined.
    An item containing the following specifications must be created for employees with release authorization:
    Workflow variant
    Initial release approval path
    Initial level
    Maximum amount
    Employees with release authorization can also be determined and assigned by user exits at each stage of the release approval procedure.
    Result
    If, when the payment run is made, the system could not determine an employee with release authorization, then it sends a message to the inbox of every person who has been assigned the task "payment release". Only after all these people have released the payment will the payment block be removed.
    If a line item is refused for release, it is forwarded to the clerk who entered it for correction. After the document has been changed, the payment release procedure begins again. If changing the line items necessitates further actions, these must be defined within the Workflow component. The event CHANGED has been preconfigured for this purpose in the standard workflow model. If you run this event, the system assumes that the line item was rejected for payment. However, the item is NOT forwarded for correction to the clerk who entered it.
    If an item is cleared before it is released, the payment release procedure is terminated (event CLEARED).
    ===========================================================
    Workflow settings: The standard system contains several workflow models for payment release: One workflow framework (WS00400012) and three sub-workflows. In Customizing for Financial Accounting, you can specify which sub-workflow should be used when the workflow framework is run. You can also enter your own sub-workflows. They must however send and receive the same data from the workflow framework as the workflow models do.
    You can use the standard sub-workflows (WS00400011, WS00400021, and WS00400022) to carry out a one, two, or three-level payment release procedure. If you require more than three release levels, you can copy the workflow models, enhance them and then enter the enhanced workflow definition in Customizing for Financial Accounting.
    Event Linkage for the Event CREATED
    If an amount requires a payment release, the event CREATED is triggered when a document is posted.
    In this case, you must go into the workflow framework in the Workflow Workbench and enter the event linkage for this event, as described below:
    Data for Event Linkage
    Object type
    BSEG
    Event
    CREATED
    Receiver type
    WS00400012
    Receiver module
    SWW_WI_CREATE_VIA_EVENT
    Check Function
    Receiver type
    FM (function module)
    Global
    X
    Enabled
    X
    Standard Tasks for the Event CREATED
    The standard system contains two standard tasks that are triggered from the workflow mailbox and used in the workflow models.
    Payment release (line item)
    Change (line item)
    Creating and Assigning Organizational Objects for Payment Release
    You must assign organizational objects (organizational units, jobs, positions) to the standard tasks. These organizational objects can be created either in Personnel Planning and Development, via the Workflow Workbench, or in Customizing for Financial Accounting (assignment of release authorization to employees).
    When you create organizational units, you must assign them to jobs or positions. You can then assign users to the positions.
    Examples for assignments:
    Organizational unit X < Position Y < User
    Organizational unit X < Job Y < Position Z < User
    In Customizing for Financial Accounting, you can assign organizational objects to the workflow variant, the release approval path, the release approval level, and the amount. These objects then release the amount depending on these criteria.
    The organizational objects for payment release defined in Customizing for Financial Accounting are automatically assigned in the background to the standard payment release task (TS00407862).
    The organizational objects for changing line items after they have been rejected for payment must be assigned to the standard task "Change line item" (TS00407864), either in Personnel Planning and Development, or via the Workflow Workbench. Alternatively, you can define the task as a general task (Additional data -> Classification).
    Changing Line Items
    The workflow models described above all contain a pre-configured event (CHANGED), which triggers other events in the same fashion as a rejection does. This event can be triggered by change documents. You must define it via the Workflow Workbench.
    Hope I had been able to help you. Please assign points.
    Rgds
    Manish

  • Mysql Workbench 5.1.2 PKGBUILD. Help needed.

    Hi,
    I'm trying to install the recently released mysql-workbench for linux.
    I wrote a PKGBUILD:
    pkgname=mysql-workbench
    pkgver=5.1.2
    pkgrel=1
    pkgdesc="A cross-platform, visual database design tool developed by MySQL"
    arch=('i686' 'x86_64')
    url="http://dev.mysql.com/workbench/"
    license=('GPL')
    groups=()
    depends=(libmysqlclient lua libglade libxml2 libsigc++2.0 libzip gtkmm freeglut pcre libgnome gtk2 pango cairo e2fsprogs)
    makedepends=(autoconf automake libtool gcc ctemplate)
    provides=()
    conflicts=()
    replaces=()
    backup=()
    options=()
    install=
    source=(ftp://ftp.mysql.com/pub/mysql/download/gui-tools/$pkgname-$pkgver-alpha-linux.tar.gz)
    noextract=()
    md5sums=('c60b3d3542f7a5d113a422c062ec3050')
    build() {
    cd "$srcdir/$pkgname-$pkgver-alpha-linux"
    ./autogen.sh --prefix=/usr
    make || return 1
    make DESTDIR="$pkgdir/" install
    Build instructions are located here: http://dev.mysql.com/workbench/?page_id=152
    I think all the dependencies are listed, and it compiles fine, but when I launch the app it segfaults:
    $> mysql-workbench
    ** Message: MWB_PLUGIN_DIR is unset! Setting MWB_PLUGIN_DIR to predifined value '../lib/mysql-workbench'
    (mysql-workbench-bin:18056): Gtk-CRITICAL **: gtk_notebook_set_tab_label: assertion `GTK_IS_WIDGET (child)' failed
    (mysql-workbench-bin:18056): Gtk-CRITICAL **: gtk_notebook_set_tab_label: assertion `GTK_IS_WIDGET (child)' failed
    (mysql-workbench-bin:18056): Gtk-CRITICAL **: gtk_notebook_set_tab_label: assertion `GTK_IS_WIDGET (child)' failed
    MGGladeXML: _xml -> 0x8a38b90
    ** Message: Trying to load module '/usr/lib/mysql-workbench/modules/db.mysql.editors.wbp.so' (cpp)
    ** Message: Trying to load module '/usr/lib/mysql-workbench/modules/db.mysql.grt.so' (cpp)
    ** Message: Trying to load module '/usr/lib/mysql-workbench/modules/dbutils.grt.so' (cpp)
    ** Message: Trying to load module '/usr/lib/mysql-workbench/modules/forms.grt.so' (cpp)
    ** Message: Trying to load module '/usr/lib/mysql-workbench/modules/wb.model.editors.wbp.so' (cpp)
    ** Message: Trying to load module '/usr/lib/mysql-workbench/modules/wb.model.grt.so' (cpp)
    /usr/bin/mysql-workbench: line 13: 18056 Segmentation fault $bindirname/mysql-workbench-bin $*
    I also tried updating the ctemplate PKGBUILD to version 0.91 (since the one in community is an old 0.4 version)
    pkgname=ctemplate
    pkgver=0.91
    pkgrel=1
    pkgdesc="A library implementing a simple but powerful template language for C++."
    arch=(i686 x86_64)
    url="http://code.google.com/p/google-ctemplate/"
    license="BSD"
    depends=('gcc')
    options=()
    source=(http://google-ctemplate.googlecode.com/files/$pkgname-$pkgver.tar.gz)
    build() {
    cd $startdir/src/$pkgname-$pkgver
    ./configure --prefix=/usr
    make || return 1
    make DESTDIR=$startdir/pkg install
    md5sums=()
    Recompiled mysql-workbench, but still segfaults as before.
    Any guess?
    Thanks.

    Never used namcap, interesting tool...
    I get some warnings but I'm not really sure how to interpret them
    $> namcap mysql-workbench-5.1.2-1-i686.pkg.tar.gz
    mysql-workbench E: Dependency detected and not included (mesa) from files ['usr/lib/mysql-workbench/libguiutil.so', 'usr/lib/mysql-workbench/libsqlparser.so.0', 'usr/lib/mysql-workbench/modules/wb.model.grt.so.0.0.0', 'usr/lib/mysql-workbench/db.wbp.so', 'usr/lib/mysql-workbench/db.mysql.wbp.so.0', 'usr/lib/mysql-workbench/libgrtui.so.0.0.0', 'usr/lib/mysql-workbench/modules/dbutils.grt.so.0.0.0', 'usr/lib/mysql-workbench/modules/wb.model.grt.so', 'usr/lib/mysql-workbench/libmforms.so.0', 'usr/bin/mysql-workbench-bin', 'usr/lib/mysql-workbench/libmdcanvasgtk.so.0.0.0', 'usr/lib/mysql-workbench/modules/db.mysql.grt.so.0.0.0', 'usr/lib/mysql-workbench/libgrt.so', 'usr/lib/mysql-workbench/libcdbc.mysql.so.0.0.0', 'usr/lib/mysql-workbench/modules/wb.model.grt.so.0', 'usr/lib/mysql-workbench/libgrtdbbe.so', 'usr/lib/mysql-workbench/libcdbc.so.0.0.0', 'usr/lib/mysql-workbench/libgrtbe.so.0.0.0', 'usr/lib/mysql-workbench/libcdbc.mysql.so', 'usr/lib/mysql-workbench/modules/forms.grt.so.0', 'usr/lib/mysql-workbench/libcdbc.so', 'usr/lib/mysql-workbench/db.wbp.so.0', 'usr/lib/mysql-workbench/libgrtsqlparser_mysql.so', 'usr/lib/mysql-workbench/libmforms.so', 'usr/lib/mysql-workbench/modules/db.mysql.editors.wbp.so', 'usr/lib/mysql-workbench/libgrtdbbe.so.0', 'usr/lib/mysql-workbench/libmforms.so.0.0.0', 'usr/lib/mysql-workbench/modules/db.mysql.editors.wbp.so.0.0.0', 'usr/lib/mysql-workbench/libgrtsqlparser_mysql.so.0.0.0', 'usr/lib/mysql-workbench/modules/dbutils.grt.so.0', 'usr/lib/mysql-workbench/modules/wb.model.editors.wbp.so', 'usr/lib/mysql-workbench/modules/forms.grt.so', 'usr/lib/mysql-workbench/libcanvasbe.so', 'usr/lib/mysql-workbench/libcanvasbe.so.0', 'usr/lib/mysql-workbench/db.wbp.so.0.0.0', 'usr/lib/mysql-workbench/libcdbc.so.0', 'usr/lib/mysql-workbench/modules/wb.model.editors.wbp.so.0.0.0', 'usr/lib/mysql-workbench/libmdcanvas.so', 'usr/lib/mysql-workbench/modules/db.mysql.grt.so', 'usr/lib/mysql-workbench/libgrt.so.0.0.0', 'usr/lib/mysql-workbench/libgrtsqlparser_mysql.so.0', 'usr/lib/mysql-workbench/libmdcanvas.so.0.0.0', 'usr/lib/mysql-workbench/libguiutil.so.0', 'usr/lib/mysql-workbench/libgrtbe.so','usr/lib/mysql-workbench/libcdbc.mysql.so.0', 'usr/lib/mysql-workbench/libsqlparser.so.0.0.0', 'usr/lib/mysql-workbench/libmdcanvasgtk.so', 'usr/lib/mysql-workbench/libcanvasbe.so.0.0.0', 'usr/lib/mysql-workbench/libgrtui.so.0', 'usr/lib/mysql-workbench/modules/db.mysql.editors.wbp.so.0', 'usr/lib/mysql-workbench/libgrt.so.0', 'usr/lib/mysql-workbench/libguiutil.so.0.0.0', 'usr/lib/mysql-workbench/libgrtdbbe.so.0.0.0', 'usr/bin/grtshell', 'usr/lib/mysql-workbench/libsqlparser.so', 'usr/lib/mysql-workbench/modules/db.mysql.grt.so.0', 'usr/lib/mysql-workbench/db.mysql.wbp.so', 'usr/lib/mysql-workbench/libgrtui.so', 'usr/lib/mysql-workbench/modules/wb.model.editors.wbp.so.0', 'usr/lib/mysql-workbench/modules/forms.grt.so.0.0.0', 'usr/lib/mysql-workbench/db.mysql.wbp.so.0.0.0', 'usr/lib/mysql-workbench/libmdcanvas.so.0', 'usr/lib/mysql-workbench/modules/dbutils.grt.so', 'usr/lib/mysql-workbench/libgrtbe.so.0', 'usr/lib/mysql-workbench/libmdcanvasgtk.so.0']
    mysql-workbench E: Dependency detected and not included (ctemplate) from files ['usr/lib/mysql-workbench/modules/db.mysql.grt.so', 'usr/lib/mysql-workbench/modules/db.mysql.grt.so.0', 'usr/lib/mysql-workbench/modules/db.mysql.grt.so.0.0.0', 'usr/lib/mysql-workbench/modules/wb.model.grt.so', 'usr/lib/mysql-workbench/modules/wb.model.grt.so.0.0.0', 'usr/lib/mysql-workbench/modules/wb.model.grt.so.0']
    mysql-workbench W: Dependency included but already satisfied (libxml2)
    mysql-workbench W: Dependency included but already satisfied (libsigc++2.0)
    mysql-workbench W: Dependency included and not needed (freeglut)
    mysql-workbench W: Dependency included but already satisfied (pcre)
    mysql-workbench W: Dependency included but already satisfied (gtk2)
    mysql-workbench W: Dependency included but already satisfied (pango)
    mysql-workbench W: Dependency included but already satisfied (cairo)
    mysql-workbench W: File (usr/lib/mysql-workbench/db.mysql.wbp.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/db.wbp.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libcanvasbe.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libcdbc.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libcdbc.mysql.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libgrt.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libgrtbe.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libgrtdbbe.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libgrtsqlparser_mysql.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libgrtui.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libguiutil.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libmdcanvas.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libmdcanvasgtk.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libmforms.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/libsqlparser.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/modules/db.mysql.editors.wbp.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/modules/db.mysql.grt.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/modules/dbutils.grt.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/modules/forms.grt.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/modules/wb.model.editors.wbp.la) is a libtool file.
    mysql-workbench W: File (usr/lib/mysql-workbench/modules/wb.model.grt.la) is a libtool file.
    It seems I missed the mesa dependency (but is a dependency of freeglut I think, which is listed)
    I also guessed wrong inserting ctemplate as a makedepends. Moved to depends now, but I had it installed anyway.
    I'm not sure about the "Dependency included but already satisfied" and "is a libtool file" warnings though...

  • Error while assigning user for release approval path for payment release

    Hi everyone,
         I am trying to assign user for payment release in SPRO. I have defined upto 'Define relevant document types for release for payment', after that while assigning user in terms of position for release and save it, i am getting error 'Program error: ASSIGN with length 0 in program "MP120800" '.Because of it i can t proceed further.
    The data in details below;
    1. Create Workflow Variant for Release for Payment
       1000     SAP
    2. Assign Company Code Workflow Variant for Release for Payment
      1000     1000     SAP
    3. Define Release Approval Groups for Release for Payment
      0001     Vendor A
    0002     vendor B
    0003     Vendor C
    0004     G/L accounts
    4. Define Release Approval Paths for Release for Payment
      0001     Vendor high
    0002     Vendor middle
    0003     Vendor low
    0004     G/L accounts
    0005     Other
    5. Assign Release Approval Paths for Release for Payment
      1000     KZ     0001     0001
    1000     KZ     0002     0002
    1000     KZ     0003     0003
    6. Assign Release Approval Procedure for Release for Payment
    1000     0001     20,000.00     KES     1     WS10000052     WS00400011
    1000     0002     50,000.00     KES     2     WS10000052     WS00400021
    1000     0003     1,000,000.00     KES     3     WS10000052     WS00400022
    7. Define Relevant Document Types for Release for Payment
         1000     KR
    1000     KZ
    8. Define Users with Authorization to Payment Release
    1000     0001     1     20,000.00     KES
    1000     0001     2     50,000.00     KES
    1000     0001     3     100,000.00     KES
    here i have selected the option and tried to create Orgobject, i am getting following error
    Program error: ASSIGN with length 0 in program "MP120800"
    If any corrections in the definitions, Please let me know.
    Thanks in advance!!

    Hello,
    Please start the report RSWOGIND, set also the checkbox "generate all
    ObjTypes from new". This should solve the problem.
    Best regards, Hana

  • Workflow for payment release

    Hello ,
    I  have done the configuration of workflow variant for payment release but  the invoice with the payment block can be  paid without any release approval  .
    Find below the configuration done for it . SPRO-Accounts Receivable and Payable-Business Transactions-Release for payment
    1.t.code PPoce: Users is assigned to each position and this was assigned to approval path
    2. Create workflow variant
    subworkflowWS00400012
    3.Assign Company code to workflow variant
    4.Define Release Approval Groups for Release for Payment
    5.Define Release Approval Paths for Release for Payment
    6.Assign Release Approval Paths for Release for Payment
    7.Assign Release Approval Procedure for Release for Payment
    2010-2010-1000-inr-WS00400012-WS00400011
    9.Define Users with Authorization to Payment Release
    11.Define Payment Block Reason for Payment Release ( payment block P selected with a tick in Not changeable )
    Then in the vendor master i have inputted the relase group also  and the payment term which is having the block .
    While executing f-02 , debiting the expense and crediting the vendor , I get the following error Line item not relevant for payment release for which  i changed the message to warning and saved it . but when i executed f-53, it doesnt go for approval .
    But in my inbox . the item is flowed with red colour and the erro log is
    Error in workflow Customizing of payment release
    Message no. FP162
    Diagnosis
    The system could not determine a subworkflow for the payment release. Check the workflow Customizing for the payment release, in particular the settings for transaction OBWE and the preceeding settings.
    The message is output from the method SUBWFDETERMINE of the BOR object BSEG.
    System Response
    The workflow was started, but the system could not create an executable dialog workitem for the line item payment release. However, you cannot release the document directly, it must be released in the workflow. A subworkflow for the payment release must be determined in the sample workflow WS00400012; the clerks are determined in role 00400125.
    Role 00400125 is based on the function module PR_WF_ACTOR1_DET.
    Procedure
    Change the payment release Customizing in Accounts Payable/Accounts Receivable Accounting. SAP delivers a sample subworkflow for payment release, WS00400011.
    Procedure for System Administration
    Restart the incorrect workflow (transaction SWPR) once you have maintained the Customizing for the payment release.
    Kindly guide me . and let me  know which setting i have missed .
    thanks

    Hi,
    Have you tested those workflows separately? I can't even view WS00400012 in my ECC 6.0 system!
    The workflows supplied by SAP are usually pretty bare-bones. More ofthen than not you have to copy them and fix them up.
    You might be able to test them via SWUS or trigger them via SWUE.
    If you create a new copy, remember to put that in the customizing.
    hope this helps
    Paul

  • Workflow WS00400012 Release for Payment not getting triggred

    Hi,
    As mentioned in the help docs we have done the following settings for Release for payment, yet the Workflow is not getting triggered.
    SPRO->Financial Accounting (New)->Accounts Receivable and Accounts Payable->Business Transactions->Release for Payment                                             
    Create Workflow Variant for Release for Payment                                             
    XX01     WS004MSBT Payment release                                        
         Workflow var.   XX01                                        
         Currency        INR                                        
         WF var.name     WS004MSBT Payment release                                        
         Prelimenary posting release                                        
          Release from    1.00                                        
          Subworkflow     WS00400012                                        
         Payment release                                        
         Release payment          X                              
         Creater permitted          X                              
          Payt release    1.00                                        
          Pmnt rel.var.   CC                                        
    Assign Company Code Workflow Variant for Release for Payment                                             
         Compamy Code     Workflow Var     WF Var. Name                              
         XXXX     XX01     WS004 Payment release                              
    Define Release Approval Groups for Release for Payment                                             
         0001     Vendor A                                   
         0002     vendor B                                   
         0003     Vendor C                                   
         0004     G/L accounts                                   
    Define Release Approval Paths for Release for Payment                                             
         0001     Vendor high                                   
         0002     Vendor middle                                   
         0003     Vendor low                                   
         0004     G/L accounts                                   
         0005     Other                                   
    Assign Release Approval Paths for Release for Payment                                             
         Workflow Variant      Doc. Type      Release Group     Approval Path                         
         XX01     KR     0001     0001                         
         XX01     KR     0002     0002                         
         XX01     KR     0003     0003                         
         XX01     KZ     0001     0001                         
         XX01     KZ     0002     0002                         
         XX01     KZ     0003     0003                         
         XX01     SA     0001     0001                         
         XX01     SA     0002     0002                         
         XX01     SA     0003     0003                         
    Assign Release Approval Procedure for Release for Payment                                             
         Wrkf      ApPath     Amt To            Curr     Rel levels     Swf Amt rel     Swf pnmt rel           
         XX01     0001     5,000.00       INR     1     WS10000052     WS00400011          
         XX01     0001     10,000.00     INR     2     WS10000053     WS00400021          
    Define Relevant Document Types for Release for Payment                                             
         Workflow Variant     Type                                   
         XX01                       KR                                   
         XX01                       KZ                                   
         XX01                     SA                                   
    Define Users with Authorization to Payment Release                                             
         XX01     1     1     5,000.00     INR                    
         Assigned Authorization Object                                        
         Production manager                                        
         XX01     1     2     10,000.00     INR                    
         Assigned Authorization Object                                        
         Comp Admin                                        
    Carry Out Function Enhancements for Release for Payment                                             
    Define Payment Block Reason for Payment Release                                             
               Free for payment                                   
         *     Skip account                                   
         A     Locked for payment                                   
         B     Blocked for payment                                   
         I     CML:InvestorContract                                   
         N     Postprocess inc.pmnt                                   
         P     Payment request                                   
         R     Invoice verification                                   
         V     Payment clearing                                   
    We are using Tcode FV60 for Park Vendor invoice                                        
    We are trying to post the Document thru Tcode FBV0 , But the Post field is grey and system shows error: func not possible as document is in not released. The Workflow is not getting triggered. And hence its not possible to release the doc.
    The workflows have been activcated
    We have done Eventlinkage and activated it.

    In future when you post question please do some formatting. It seems like a novel.
    Have you checked in SWEL whether the event CREATED of Business Object BSEG getting triggered. I hope you have activated the linkage between event and workflow from PFTC or SWE2 transaction code.
    Thanks
    Arghadip

  • Oracle workbench

    Does "Oracle Migration Workbench Release 10.1.0.4.0" support mysql ?
    if so where can i find the plugin for non oracle database
    it shows only "IBM and Informix" on plugin
    when i create Repository i get
    "No plugins are installed. please install the plugin for the database you want to migrate"
    Pls let me know and suggest me.
    One more thing
    if is use "sqldeveloper" and try to migrate from mysql to oracle its taking very very long time and stops error capturing failed.

    Interesting question. I suspect it is related to the 'I have a question about SQL Developer' forum rather than the 'I have a problem obtaining software' forum.
    You might want to go to the forum home (http://forums.oracle.com), scroll down to Databases, click on 'More ...', and select 'SQL Developer' if that is indeed true.

  • How we make button in accept release button fbvo for workflow trigger

    Hi Experts
    I did workflow configuration, fin a/c- fin a/c global setting- doc - doc parking-
    Create Workflow Variant for Parking Documents
    Assign Company Code to a Workflow Variant for Parking Documents
    Define Release Approval Groups for Parking Documents
    Define Release Approval Paths for Parking Documents
    Assign Release Approval Paths for Parking Documents
    Assign Release Approval Procedure for Parking Documents
    Define Users with Release Authorization for Parking Documents
    before that i did workflow builder as well and i activated. but in fbv0 i am not getting any extra button then how it will work i dont know. Please further what i do...

    Hi,
    Please note that in FBV0, workflow will get triggered automatically the moment you park/complete the document and as per the settings done in the Workflow Variant. There will not be any separate button to release a Workflow because it is automatic and gets triggered based on Events defined in it.
    Regards,
    Kiron Kumar T.

  • PO Release Strategy on Value Based

    Dear All My Friends,
    i want to define the following Release Strategy, please advice how it will be done
    Person A will Release PO  value <=50,000/-
    Person B will Release PO Value >50000 and <=100000
    Person C will Release PO Value >100000
    please help me
    Thanks and Regards,
    Rajesh G

    Hi,
    SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
    Three steps involved in release process of purchase order.
    1) Edit Characteristic: -
    Create characteristic for release purchase order. If you want to release purchase order on total value. So you can create characteristic for Total net value. Take reference of CEKKO structure and GNETW field for Total net value in additional data of characteristic. E.g :- Total net value u2013 GNETWu2026Click on intervals allowed check box ..
    2) Edit Class: -
    After creation of characteristic, create class for release purchase order. In which you can take reference of
    Class Type: - 032,
    Status: - Release,
    Class group: - Release strategy class,
    And put reference of your characteristic, which are created by you in first step.
    E.g: - Class u2013 REL_PO
    3)Define Release Procedure of purchase order: -
    In this step four processes involved.
    1) Release Groups
    2) Release Codes
    3) Release indicator
    4) Release Strategies
    1) Release Group: - In which you can define release strategy group
    For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    2) Release code: - In which you can define release code. Enter value as
    Release group: - 01,release code: -01 u2013 Purchase Head,
    Release group: -01, release code: - 02 u2013 Auditor.
    3) Release indicator: - In this step you have to define release indicator.
    Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
    4) Release Strategy: - This is the final step for release strategy.
    Assign release code 01, 02.
    Click on release prerequisites, select 02 u2013 check box and click on continue.
    Click on release status button, enter release indicator X, I, S and click continue
    Click on classification button, Enter values of Total net value for which you want to created release strategy.
    Person A will Release PO value <=50,000/-
    Person B will Release PO Value >50000 and <=100000
    Person C will Release PO Value >100000
    Utsav

  • Release of parked document affects other document types

    Hello,
    we are using the standard parked-vendor-invoice-with-workflow scenario in production since 1, 5 years.
    Now we want to start using the parking function for customer invoices as well, but without release requirement and workflow.
    For some reason the release scenario is automatically also activated for the customer invoices (document type DR) . I. e  the "release necessary" flag is set automatically in the workflow tab strip in the parked customer invoice and the workflow (for the vendor invoice scenario)  is triggered as well for the customer invoice.
    We have configured a workflow variant and defined the document release as active from 1 SEK.  We have assigned the wf-variant to a company code.
    An approval path has been defined and assigned to the workflow variant, release approval group and the document type KR (vendor invoice). The approval path is also assigned to a workflow.
    We thought that by defining the document type specifically  in the assignment of the approval path to the combination workflow variant, release approval group and document type, we could restrict the release scenario to be activated only for a specific document type.  This does not seem to happen.  Is this a known bug?
    Kind regards
    Viveka Schwartz

    Hi,
    What is the OSS note?
    Thanks,
    Steph

  • Report of who released purchase requisitions

    Hi,
    Is it possible to get a list of which user released a group of purchase requisitions? A list display would be ideal, but if somebody could let me know a table that holds the information that'd be good also.
    Thanks,
    Richard

    Hi Richard,
    Try to use the table CDHDR where object class will be BANF & Object ID is purchase requisition number appended by "00". In this table you will be getting information about the status of your Purchase Requisition. It will give all the changes that has happened in the PR. Fetch the data gainst Tcode as ME54N & the usernames. The usernames that will appear against the tcode ME54N are the ones who are releasing the PR.
    Ask ABAP person to fetch these data & make a report.
    I hope this will help.Reward if its helpfull.
    Regards
    John

Maybe you are looking for

  • Crystal Report Viewer 2008, postback causes a weird QueryString for dates

    HI, I'm having a weird problem that was masked with the error "". What is happening to me is that i have an ASPX page where the QueryString passed in is used as parameters to the report (straightforward).  When the page first loads, this is all fine

  • Key binding in Forms 6i

    Hi All, I have a problem with key binding. I have tried different permutations of changing the key binding using the Oracle Terminal on FMRUSW.RES FILE to no avail. I have edited the keys of windows-sqlforms normal and used USER DEFINED KEY 2, etc bu

  • Creating an iPhoto project book....how can I add photos to the photo pane?

    I am creating a book from our recent vacation. Each day of the vacation I have separated into different Events. I chose the first day/event and clicked create book.....have placed all the photos in various "slots" in the book and now want to add phot

  • Can I search applications in just a language that I want?

    Please help!!! ......Can I search applications in just a language that i want?

  • Get Web Dynpro object name

    Hi colleagues, I am new to Web Dynpro. I would like to know how can I get current Web Dynpro object name from user interface on Portal - to open source code in SE80? Is it possible to use in Web Dynpro something like "/h" in backend command line? - t