PO Status Unapproved

Hi All
Whenever Iam trying to add a new PO, the status is showing as Unapproved.
Document is adding successfully, but Copy To button is disabled.
There are no approvals.
Please tell me about this pecular thing
Thanks

Hi Bandaru,
IF you want to Active Copy to button in Purchase Order for all User.
Do this,
->> Administrator.
->> System Initialization.
->> Document Settings.
->> Choose Per Document Tab.
->> Select Purchase Order in Document Selection.
->> put the Tick Mark in Purchase Order Approved
UPDATE the Document Setting.
OR
IF you want to Active Copy to button in require Purchase Order.
Do this,
->> UnCheck the Tick Mark in Purchase Order Approved in Per Document Tab on Document Setting.
and
->> Open the require PO document.
->> put the Tick Mark in Approved Check box at Logistics Tab on Purchase Order Doc.
Regards,
Madhan.

Similar Messages

  • Sales Order Status Unapproved

    Hi,
    Can anybody tell me how to make a sales order status as 'unapproved'?
    Thanks and Regards
    Surabhi

    Hi Surabhi,
    Do you know how to change the status from unapproved to open for a sales orders please?
    Thanks
    best regards
    Sarah

  • Error: ORA-04030: out of process memory when trying to allocate 20060 bytes

    I have tow portioned of query and uniond all it it gives error like ORA-04030: out of process memory when trying to allocate 20060 bytes
    NOTE : PARTY ONE AND PART 2 INDUALY WORKS WELL BUTT IT GIVESS ERROR AT THE TIME OF UNION ALL
    Please i m waiting for sharp response
    -------------------------------------PART ONE START --------------------------------------------------------------------------
    SELECT * FROM
    SELECT
    TO_CHAR(SOURCE) AS SOURCE,
    ORG_ID,
    -- 'HUSSNAIN' AS VENDOR_TYPE,
    INV_PAY_VOUCHER,
    INV_PAY_TYPE,
    INV_PAY_NUM,
    INV_PAY_VEN_ID,
    INV_PAY_VEN_NAME,
    INV_PAY_SITE,
    INV_PAY_DATE,
    INV_PAY_GROSS,
    INV_PAY_AMT,
    INV_PAY_DESC,
    INV_PAY_HTAX,
    INV_AMT,
    INV_GST,
    INV_PAY_AMT INVOICE_AMOUNT,
    INV_GST_T INV_TOTAL_TAX,
    NVL(DEBIT,0) AS DEBIT1,
    NVL(CREDIT,0) AS CREDIT1,
    VENDOR_SITE_NAME AS SITE_CODE,
    INVOICE_DATE,
    CHECK_NUMBER,
    PAYMENT_DATE,
    GL_CODE,
    GL_CODE_DESC,
    SUPPLIER_ID,
    STATUS ,
    COUNT(INV_PAY_DATE) AS TRANSACTION,
    LINE,
    SELECT
    SUM(NVL(VX.DEBIT,0)) - SUM(NVL(VX.CREDIT,0)) OPN_BAL
    FROM XX_AP_INVPAY_COMBINE_V1 VX
    WHERE
    SUBSTR(VX.INV_PAY_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE1,1,10),'YYYY-MM-DD')
    -- AND
    -- SUBSTR(VX.INVOICE_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE_INVOICE1,1,10),'YYYY-MM-DD')
    AND VX.INV_PAY_SITE = nvl(:P_SITE_ID, VX.INV_PAY_SITE)
    AND VX.Vendor_Site_name = nvl(:P_VENDOR_SITE_NAME , VX.Vendor_Site_name)
    AND VX.INV_PAY_VEN_ID = nvl(:P_VEN_ID,INV_PAY_VEN_ID)
    AND VX.ORG_ID = nvl(:P_ORG_ID,ORG_ID)
    AND VX.SOURCE = NVL (:P_TRANSACTION_TYPE,VX.SOURCE)
    AND vx.status = 'Approved'
    AND VX.INV_PAY_SITE =V.INV_PAY_SITE
    AND VX.Vendor_Site_name=V.VENDOR_SITE_NAME
    AND VX.INV_PAY_VEN_ID=V.INV_PAY_VEN_ID
    and vx.status = v.status
    -- AND VX.SOURCE=V.SOURCE
    -- &pwhereclause
    ) AS O_BALANCE_APPROVED,
    SELECT
    SUM(NVL(VX.DEBIT,0)) - SUM(NVL(VX.CREDIT,0)) OPN_BAL
    FROM XX_AP_INVPAY_COMBINE_V1 VX
    WHERE
    SUBSTR(VX.INV_PAY_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE1,1,10),'YYYY-MM-DD')
    -- AND
    -- SUBSTR(VX.INVOICE_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE_INVOICE1,1,10),'YYYY-MM-DD')
    AND VX.INV_PAY_SITE = nvl(:P_SITE_ID, VX.INV_PAY_SITE)
    AND VX.Vendor_Site_name = nvl(:P_VENDOR_SITE_NAME , VX.Vendor_Site_name)
    AND VX.INV_PAY_VEN_ID = nvl(:P_VEN_ID,INV_PAY_VEN_ID)
    AND VX.ORG_ID = nvl(:P_ORG_ID,ORG_ID)
    AND VX.SOURCE = NVL (:P_TRANSACTION_TYPE,VX.SOURCE)
    and vx.status = 'Unapproved'
    AND VX.INV_PAY_SITE =V.INV_PAY_SITE
    AND VX.Vendor_Site_name=V.VENDOR_SITE_NAME
    AND VX.INV_PAY_VEN_ID=V.INV_PAY_VEN_ID
    and vx.status = v.status
    -- AND VX.SOURCE=V.SOURCE
    -- &pwhereclause
    ) AS O_BALANCE_UPAPPROVED,
    SELECT
    SUM(NVL(VX.DEBIT,0)) - SUM(NVL(VX.CREDIT,0)) OPN_BAL
    FROM XX_AP_INVPAY_COMBINE_V1 VX
    WHERE
    SUBSTR(VX.INV_PAY_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE1,1,10),'YYYY-MM-DD')
    -- AND SUBSTR(VX.INVOICE_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE_INVOICE1,1,10),'YYYY-MM-DD')
    AND VX.INV_PAY_SITE = nvl(:P_SITE_ID, VX.INV_PAY_SITE)
    AND VX.Vendor_Site_name = nvl(:P_VENDOR_SITE_NAME , VX.Vendor_Site_name)
    AND VX.INV_PAY_VEN_ID=nvl(:P_VEN_ID,INV_PAY_VEN_ID)
    AND VX.ORG_ID = NVL(:P_ORG_ID,ORG_ID)
    AND VX.SOURCE = NVL (:P_TRANSACTION_TYPE,VX.SOURCE)
    AND vx.status = v.status
    AND VX.INV_PAY_SITE =V.INV_PAY_SITE
    AND VX.Vendor_Site_name=V.VENDOR_SITE_NAME
    AND VX.INV_PAY_VEN_ID=V.INV_PAY_VEN_ID
    -- AND VX.SOURCE=V.SOURCE
    -- &pwhereclause
    ) AS O_BALANCE
    FROM XX_AP_INVPAY_COMBINE_V1 V
    WHERE
    SUBSTR (V.INV_PAY_DATE,1,10) BETWEEN NVL( TO_DATE(SUBSTR(:P_DATE1,1,10),'YYYY-MM-DD'),SUBSTR(V.INV_PAY_DATE,1,10)) AND nvl(TO_DATE(SUBSTR(:P_DATE2,1,10),'YYYY-MM-DD') ,SUBSTR(V.INV_PAY_DATE,1,10))
    -- AND
    -- SUBSTR(V.INVOICE_DATE,1,10) BETWEEN nvl( TO_DATE(SUBSTR(:P_DATE_INVOICE1,1,10),'YYYY-MM-DD'),SUBSTR(V.INVOICE_DATE,1,10)) AND nvl(TO_DATE(SUBSTR(:P_DATE_INVOICE2,1,10),'YYYY-MM-DD') ,SUBSTR(V.INVOICE_DATE,1,10))
    AND V.INV_PAY_SITE=nvl(:P_SITE_ID,INV_PAY_SITE)
    AND V.VENDOR_SITE_NAME = NVL(:P_VENDOR_SITE_NAME , V.VENDOR_SITE_NAME)
    AND V.INV_PAY_VEN_ID=nvl(:P_VEN_ID,V.INV_PAY_VEN_ID)
    AND V.ORG_ID=nvl(:P_ORG_ID,V.ORG_ID)
    AND V.SOURCE = NVL (:P_TRANSACTION_TYPE,V.SOURCE)
    -- ORDER BY INV_PAY_DATE,CHECK_NUMBER,INV_PAY_VOUCHER asc ,Debit1 desc ,credit1 DESC
    GROUP BY
    SOURCE,
    ORG_ID,
    -- 'HUSSNAIN' AS VENDOR_TYPE,
    INV_PAY_VOUCHER,
    INV_PAY_TYPE,
    INV_PAY_NUM,
    INV_PAY_VEN_ID,
    INV_PAY_VEN_NAME,
    INV_PAY_SITE,
    INV_PAY_DATE,
    INV_PAY_GROSS,
    INV_PAY_AMT,
    INV_PAY_DESC,
    INV_PAY_HTAX,
    INV_AMT,
    INV_GST,
    INV_PAY_AMT,
    INV_GST_T,
    DEBIT,
    CREDIT,
    VENDOR_SITE_NAME,
    INVOICE_DATE,
    CHECK_NUMBER,
    PAYMENT_DATE,
    GL_CODE,
    GL_CODE_DESC,
    SUPPLIER_ID,
    STATUS,
    LINE
    ORDER BY
    INV_PAY_DATE,
    CHECK_NUMBER,
    --V.SOURCE asc,
    INV_PAY_NUM,
    LINE,
    --INV_PAY_DESC,
    INV_PAY_VOUCHER
    ) A
    -------------------------------------PART ONE END --------------------------------------------------------------------------
    -------------------------------------PART TWO START --------------------------------------------------------------------------
    UNION ALL
    SELECT * FROM
    SELECT * FROM
    SELECT
    DISTINCT
    NULL AS SOURCE,
    ORG_ID,
    NULL AS INV_PAY_VOUCHER,
    NULL AS INV_PAY_TYPE,
    NULL AS INV_PAY_NUM,
    INV_PAY_VEN_ID,
    INV_PAY_VEN_NAME,
    INV_PAY_SITE,
    NULL AS INV_PAY_DATE,
    NULL AS INV_PAY_GROSS,
    NULL AS INV_PAY_AMT,
    NULL AS INV_PAY_DESC,
    NULL AS INV_PAY_HTAX,
    NULL AS INV_AMT,
    NULL AS INV_GST,
    NULL AS INVOICE_AMOUNT,
    NULL AS INV_TOTAL_TAX,
    NULL AS DEBIT1,
    NULL AS CREDIT1,
    NULL AS SITE_CODE,
    NULL AS INVOICE_DATE,
    NULL AS CHECK_NUMBER,
    NULL AS PAYMENT_DATE,
    NULL AS GL_CODE,
    NULL AS GL_CODE_DESC,
    SUPPLIER_ID,
    NULL AS STATUS ,
    NULL AS TRANSACTION,
    NULL AS LINE,
    SELECT
    SUM(NVL(VX.DEBIT,0)) - SUM(NVL(VX.CREDIT,0)) OPN_BAL
    FROM XX_AP_INVPAY_COMBINE_V1_OP VX
    WHERE
    SUBSTR(VX.INV_PAY_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE1,1,10),'YYYY-MM-DD')
    -- AND
    -- SUBSTR(VX.INVOICE_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE_INVOICE1,1,10),'YYYY-MM-DD')
    AND VX.INV_PAY_SITE = nvl(:P_SITE_ID, VX.INV_PAY_SITE)
    AND VX.Vendor_Site_name = nvl(:P_VENDOR_SITE_NAME , VX.Vendor_Site_name)
    AND VX.INV_PAY_VEN_ID = nvl(:P_VEN_ID,INV_PAY_VEN_ID)
    AND VX.ORG_ID = nvl(:P_ORG_ID,ORG_ID)
    AND VX.SOURCE = NVL (:P_TRANSACTION_TYPE,VX.SOURCE)
    AND vx.status = 'Approved'
    AND VX.INV_PAY_SITE =V.INV_PAY_SITE
    AND VX.Vendor_Site_name=V.VENDOR_SITE_NAME
    AND VX.INV_PAY_VEN_ID=V.INV_PAY_VEN_ID
    and vx.status = v.status
    -- AND VX.SOURCE=V.SOURCE
    -- &pwhereclause
    ) AS O_BALANCE_APPROVED,
    SELECT
    SUM(NVL(VX.DEBIT,0)) - SUM(NVL(VX.CREDIT,0)) OPN_BAL
    FROM XX_AP_INVPAY_COMBINE_V1_OP VX
    WHERE
    SUBSTR(VX.INV_PAY_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE1,1,10),'YYYY-MM-DD')
    -- AND
    -- SUBSTR(VX.INVOICE_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE_INVOICE1,1,10),'YYYY-MM-DD')
    AND VX.INV_PAY_SITE = nvl(:P_SITE_ID, VX.INV_PAY_SITE)
    AND VX.Vendor_Site_name = nvl(:P_VENDOR_SITE_NAME , VX.Vendor_Site_name)
    AND VX.INV_PAY_VEN_ID = nvl(:P_VEN_ID,INV_PAY_VEN_ID)
    AND VX.ORG_ID = nvl(:P_ORG_ID,ORG_ID)
    AND VX.SOURCE = NVL (:P_TRANSACTION_TYPE,VX.SOURCE)
    and vx.status = 'Unapproved'
    AND VX.INV_PAY_SITE =V.INV_PAY_SITE
    AND VX.Vendor_Site_name=V.VENDOR_SITE_NAME
    AND VX.INV_PAY_VEN_ID=V.INV_PAY_VEN_ID
    and vx.status = v.status
    -- AND VX.SOURCE=V.SOURCE
    -- &pwhereclause
    ) AS O_BALANCE_UPAPPROVED,
    (SUM(NVL(V.DEBIT,0)) - SUM(NVL(V.CREDIT,0))) AS O_BALANCE
    FROM XX_AP_INVPAY_COMBINE_V1_OP V
    WHERE
    SUBSTR(V.INV_PAY_DATE,1,10) < TO_DATE(SUBSTR(:P_DATE1,1,10),'YYYY-MM-DD')
    AND V.INV_PAY_SITE=nvl(:P_SITE_ID,INV_PAY_SITE)
    AND V.VENDOR_SITE_NAME = NVL(:P_VENDOR_SITE_NAME , V.VENDOR_SITE_NAME)
    AND V.INV_PAY_VEN_ID=nvl(:P_VEN_ID,V.INV_PAY_VEN_ID)
    AND V.ORG_ID=nvl(:P_ORG_ID,V.ORG_ID)
    AND
    ( (SELECT (SUM(NVL(V.DEBIT,0)) - SUM(NVL(V.CREDIT,0))) FROM XX_AP_INVPAY_COMBINE_V1_OP V
    WHERE
    SUBSTR (V.INV_PAY_DATE,1,10) BETWEEN NVL( TO_DATE(SUBSTR(:P_DATE1,1,10),'YYYY-MM-DD'),SUBSTR(V.INV_PAY_DATE,1,10)) AND nvl(TO_DATE(SUBSTR(:P_DATE2,1,10),'YYYY-MM-DD') ,SUBSTR(V.INV_PAY_DATE,1,10))
    -- AND
    -- SUBSTR(V.INVOICE_DATE,1,10) BETWEEN nvl( TO_DATE(SUBSTR(:P_DATE_INVOICE1,1,10),'YYYY-MM-DD'),SUBSTR(V.INVOICE_DATE,1,10)) AND nvl(TO_DATE(SUBSTR(:P_DATE_INVOICE2,1,10),'YYYY-MM-DD') ,SUBSTR(V.INVOICE_DATE,1,10))
    AND V.INV_PAY_SITE=nvl(:P_SITE_ID,INV_PAY_SITE)
    AND V.VENDOR_SITE_NAME = NVL(:P_VENDOR_SITE_NAME , V.VENDOR_SITE_NAME)
    AND V.INV_PAY_VEN_ID=nvl(:P_VEN_ID,V.INV_PAY_VEN_ID)
    AND V.ORG_ID=nvl(:P_ORG_ID,V.ORG_ID)
    AND V.SOURCE = NVL (:P_TRANSACTION_TYPE,V.SOURCE)) IS NULL
    GROUP BY
    ORG_ID,
    INV_PAY_VEN_ID,
    INV_PAY_VEN_NAME,
    INV_PAY_SITE,
    SUPPLIER_ID,
    V.VENDOR_SITE_NAME,
    V.STATUS
    --UNION ALL
    ) B
    -------------------------------------PART TWO END --------------------------------------------------------------------------

    Hi,
    This error is typically associated with the OS being unable to allocate any more memory to a process. It typically manifests itself in 32 bit operating systems, especially Windows, where processes are limited to a maximum 2Gb, but with the way memory is allocated, 1.5Gb tends to be a more realistic limit. With an Oracle instance this means that the total memory requirements, SGA and PGA, should not exceed about 1.5Gb. In Windows, because connection processes also run as threads of the server process, these are also part of the calculation.
    The way then to avoid, or at least reduce this error, is to reduce the memory requirements of the database instance. Also, because some operating systems do not release unused process memory very easily, regular bounces of the database may also help avoid the error, provided you have the luxury to do this.
    The long term fix to this error would be to upgrade to a 64 bit operating system, where this limit is greatly increased. There is also a feature of 32 bit windows that can be added (forget what its called) that increases the 2Gb limit to 3Gb.
    Regards
    Andre

  • Problems in output messages for PO.

    Hi Experts,
    We have a problems with output messages determination, if I have the PO without release approval the system send the output messages ( NEU ) I need that determination doesn't occurs when the po status is unapproved.
    For Explo: I create the PO 45...01 with status unapproved, the system generate tehe messages ( NEU ) but doesnt send to destination, the send only happened when i make the realese.
    There is a file with more details.
    [http://www.easy-share.com/1904410163/POunapproved.doc]
    Thanks,
    Gustavo

    Hi,
    In the release strategy,if the indicator changeablity is 1 the system will not allow you to take repeat out put.
    Solution is that you have to change the release indicator changeability to 6(SPRO>MM>Purchasing>Purchase order>Define release procedure for purchase order>Release indicator>Changeability).
    Another option is that in the message output of the PO in further data change despatch time to 3 and take a repeat out put.
    Also check,
    SPRO > MM > PO > Release Procedure for PO > Release indicator > Changeability of Purchasing Document During/After Release as 2 for Release ID - G and save
    And then Create go to chage mode of PO and repeat the messages
    Regards,
    Rahul.

  • How to do approvals only on new updates?

    We usually set deadlines on installation of updates.  The problem we have is that when the new month's updates come out and we set deadline on needed updates, it also lists all our old updates.  So, when we set new approvals and deadlines that
    are intended for new updates, it keeps moving the installation deadline forward even on very old updates.  This causes automatic installation of some very old critical updates to be delayed when a new application such as Project or Visio is installed
    on an existing workstation.  If someone installs an Office application that needs updates from prior months, we would like the updates to install immediately based on the already passed deadline.
    When we are doing monthly update approvals, how can we filter the All Updates list to show only the updates for that month so that previous old approvals are not changed.  I don't see any date filters.
    Filtering by status of "unapproved" does not work because there are auto-approval rules for our update testing groups that prevents updates from showing in the filter as approval status "Unapproved."

    There was nothing wrong with your previous practice of only approving updates that are displayed in NEEDED status. In fact, this is the recommended practice for managing update approvals.
    There may be scenarios in which an out-of-date system triggers the need to approve a legacy update that no other systems need anymore, but this should be a fairly rare occurrence.
    Obviously there's a scenario where an application is installed and needs updates, and there's also the scenario where a NEW system is put on the network and needs ALL of the available updates for that operating system. (This is where maintaining a patched
    image and using WDS or MDT can be a lifesaver.)
    I would not recommend "approve all updates whether needed or not" as a response to the occasional scenario that diverges from your normal routine. The impact of approving hundreds, if not thousands, of additional updates, plus the gigabytes of file storage
    that will be consumed, is not worth the perceived benefit.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Purchase Order has approved but Status show as Unapproved

    Dear All Experts,
    I have a Purchase Order need to go throught approval procedure. The Purchase Order has approved by user and add into system and printed out. When second time, open the same Purchase Order, the status show "Unapproved" but the Purchase Order windows header name show Purchase Order [Approved], this make user unable to copy to GRPO. I have try to restore stored procedures in SAP B1, it does not make any changes. The user is using SAP B1 2007A SP0 PL49. Please Advise.

    Hi Angie
    the purchase order once approved has to be added on to the system after approval if u say that u have added the purchase order after it got approved then that seems to be a concern for that u need to contact ur sap partner or if u are a partner then u need to get in touch with sap to resolve the isssue as it could be because of problem with ur database
    but before that please be sure off that u are using the correct way and have sucessfully added the documnt apon approval.
    Regards,
    Manish

  • Search based on UnApproved status in HRMS

    Hi All
    I have search page which shows records based on search
    that page has one dropdown list which contain many options like
    Approved,Closed,Rejected,Unapproved,etc
    when I select Approved status then It shows all records that are approved
    and when I select unapproved then it doesnt shows any records which are un approved
    now I want show all records which are unapproved after selecting unapproved status
    that page sows records in form of table at the bottom side of page
    How can I do it?

    I am getting confused plz use this Query
    SELECT Vac.VACANCY_ID, Vac.DATE_FROM, Vac.NAME, Vac.DATE_TO, Vac.DESCRIPTION, Vac.NUMBER_OF_OPENINGS, Vac.LAST_UPDATE_DATE, Vac.CREATION_DATE, Job.NAME AS JobName, Job.JOB_ID, Grade.NAME AS GradeName, Grade.GRADE_ID, Org.NAME AS OrgName, Org.ORGANIZATION_ID, Loc.LOCATION_CODE, Loc.LOCATION_ID, Recruiter.FULL_NAME AS RECRUITER_NAME, Recruiter.PERSON_ID AS RECRUITER_ID, Recruiter.EFFECTIVE_START_DATE, Recruiter.EFFECTIVE_END_DATE, Recruiter.EMAIL_ADDRESS, Manager.FULL_NAME AS MANAGER_NAME, Manager.PERSON_ID AS MANAGER_ID, Manager.EFFECTIVE_START_DATE AS MAN_EFFECTIVE_START_DATE, Manager.EFFECTIVE_END_DATE AS MAN_EFFECTIVE_END_DATE, Manager.EMAIL_ADDRESS AS EMAIL_ADDRESS1, Status.MEANING, Status.LOOKUP_TYPE, Status.LOOKUP_CODE, Vac.REQUISITION_ID, (select count(assignment_type) from per_all_assignments_f paaf where paaf.vacancy_id = Vac.vacancy_id and paaf.assignment_type = 'A' and :1 between PAAF.EFFECTIVE_START_DATE AND PAAF.EFFECTIVE_END_DATE AND NOT EXISTS (SELECT NULL FROM per_all_assignments_f paf3 WHERE paf3.vacancy_id = paaf.vacancy_id AND paf3.person_id = paaf.person_id AND paf3.assignment_type ='E' ) and exists ( select null from per_all_assignments_f paf4 where paf4.assignment_id = paaf.assignment_id and paf4.effective_end_date = to_date('31/12/4712','DD/MM/RRRR') and paf4.assignment_type = 'A' ) and (fnd_profile.value('IRC_AGENCY_NAME') is null or exists (select 1 from irc_agency_vacancies iav1 ,per_all_people_f per1 ,irc_notification_preferences inp1 where iav1.vacancy_id=vac.vacancy_id and iav1.agency_id=fnd_profile.value('IRC_AGENCY_NAME') and per1.person_id=paaf.person_id and per1.party_id=inp1.party_id and (inp1.agency_id=iav1.agency_id or iav1.manage_applicants_allowed='Y')) ) ) AS APPLICANTS, (select count(distinct assignment_id) from per_all_assignments_f paaf where paaf.vacancy_id = Vac.vacancy_id and assignment_type = 'E' ) AS FILLED, decode(vac.manager_id,:2,'Y','N') AS MY_VACANCIES, Vac.BUDGET_MEASUREMENT_TYPE, Vac.BUDGET_MEASUREMENT_VALUE, posEO.NAME AS NAME1, posEO.POSITION_ID, posEO.EFFECTIVE_START_DATE AS EFFECTIVE_START_DATE2, posEO.EFFECTIVE_END_DATE AS EFFECTIVE_END_DATE2, NULL AS ACCESS_FLAGS, Vac.STATUS AS VACANCY_STATUS, Bg.NAME AS NAME2, Bg.ORGANIZATION_ID AS ORGANIZATION_ID1, Vac.BUSINESS_GROUP_ID, VSC.EMPLOYEE, VSC.CONTRACTOR, VSC.EMPLOYMENT_CATEGORY, VSC.TRAVEL_PERCENTAGE, VSC.MIN_SALARY, VSC.MAX_SALARY, VSC.SALARY_CURRENCY, VSC.PROFESSIONAL_AREA, VSC.WORK_AT_HOME, VSC.MIN_QUAL_LEVEL, VSC.MAX_QUAL_LEVEL, VSC.ATTRIBUTE_CATEGORY, VSC.ATTRIBUTE1, VSC.ATTRIBUTE2, VSC.ATTRIBUTE3, VSC.ATTRIBUTE4, VSC.ATTRIBUTE5, VSC.ATTRIBUTE6, VSC.ATTRIBUTE7, VSC.ATTRIBUTE8, VSC.ATTRIBUTE9, VSC.ATTRIBUTE10, VSC.ATTRIBUTE11, VSC.ATTRIBUTE12, VSC.ATTRIBUTE13, VSC.ATTRIBUTE14, VSC.ATTRIBUTE15, VSC.ATTRIBUTE16, VSC.ATTRIBUTE17, VSC.ATTRIBUTE18, VSC.ATTRIBUTE19, VSC.ATTRIBUTE20, VSC.ATTRIBUTE21, VSC.ATTRIBUTE22, VSC.ATTRIBUTE23, VSC.ATTRIBUTE24, VSC.ATTRIBUTE25, VSC.ATTRIBUTE26, VSC.ATTRIBUTE27, VSC.ATTRIBUTE28, VSC.ATTRIBUTE29, VSC.ATTRIBUTE30, VSC.SEARCH_CRITERIA_ID, Vac.ATTRIBUTE_CATEGORY AS VAC_ATTRIBUTE_CATEGORY, Vac.ATTRIBUTE1 AS VAC_ATTRIBUTE1, Vac.ATTRIBUTE2 AS VAC_ATTRIBUTE2, Vac.ATTRIBUTE3 AS VAC_ATTRIBUTE3, Vac.ATTRIBUTE4 AS VAC_ATTRIBUTE4, Vac.ATTRIBUTE5 AS VAC_ATTRIBUTE5, Vac.ATTRIBUTE6 AS VAC_ATTRIBUTE6, Vac.ATTRIBUTE7 AS VAC_ATTRIBUTE7, Vac.ATTRIBUTE8 AS VAC_ATTRIBUTE8, Vac.ATTRIBUTE9 AS VAC_ATTRIBUTE9, Vac.ATTRIBUTE10 AS VAC_ATTRIBUTE10, Vac.ATTRIBUTE11 AS VAC_ATTRIBUTE11, Vac.ATTRIBUTE12 AS VAC_ATTRIBUTE12, Vac.ATTRIBUTE13 AS VAC_ATTRIBUTE13, Vac.ATTRIBUTE14 AS VAC_ATTRIBUTE14, Vac.ATTRIBUTE15 AS VAC_ATTRIBUTE15, Vac.ATTRIBUTE16 AS VAC_ATTRIBUTE16, Vac.ATTRIBUTE17 AS VAC_ATTRIBUTE17, Vac.ATTRIBUTE18 AS VAC_ATTRIBUTE18, Vac.ATTRIBUTE19 AS VAC_ATTRIBUTE19, Vac.ATTRIBUTE20 AS VAC_ATTRIBUTE20, decode((select update_allowed||delete_allowed from irc_rec_team_members rec where rec.vacancy_id = VAC.vacancy_id and rec.person_id = :3), 'NN', 'VIEW', 'UPDATE') AS TEAM_ACCESS, (select count() from hr_api_transactions where transaction_ref_table = 'PER_ALL_VACANCIES' and transaction_ref_id = Vac.vacancy_id and creator_person_id = :4 and status = 'S') AS SaveForLaterLocks, (select count(*) from hr_api_transactions where transaction_ref_table = 'PER_ALL_VACANCIES' and transaction_ref_id = Vac.vacancy_id and status != 'D' and (creator_person_id != :5 or transaction_state != null or status != 'S' )) AS TRANSACTION_LOCKS, (select decode((SELECT count(pav1.vacancy_id) FROM per_all_vacancies pav1 WHERE pav1.vacancy_id =vac.VACANCY_ID AND(pav1.status ='CLOSED' OR (pav1.date_to is not null and NOT :18 BETWEEN pav1.date_from AND pav1.date_to))),0,'Y','N') from dual) AS APPLY_FLAG, PSA.LOOKUP_TYPE AS LOOKUP_TYPE1, PSA.LOOKUP_TYPE AS LOOKUP_TYPE2, Grade.OBJECT_VERSION_NUMBER AS OBJECT_VERSION_NUMBER1, PSA.LOOKUP_CODE AS LOOKUP_CODE1, Loc.OBJECT_VERSION_NUMBER AS OBJECT_VERSION_NUMBER2, PSA.MEANING AS MEANING1, Recruiter.OBJECT_VERSION_NUMBER AS OBJECT_VERSION_NUMBER3, decode ((SELECT count(1) FROM PER_RECRUITMENT_ACTIVITIES PRA,PER_ALL_VACANCIES PAV, IRC_ALL_RECRUITING_SITES ias,PER_RECRUITMENT_ACTIVITY_FOR PRAE WHERE vac.vacancy_id=PRAE.vacancy_id AND pra.recruiting_site_id = ias.recruiting_site_id AND PRAE.RECRUITMENT_ACTIVITY_ID = PRA.RECRUITMENT_ACTIVITY_ID AND ias.EXTERNAL = 'R' AND sysdate BETWEEN pra.date_start AND NVL (pra.date_end, sysdate) ), 0,'N','Y') AS REFERRALS FROM PER_ALL_VACANCIES Vac, PER_JOBS_VL Job, PER_GRADES_VL Grade, HR_ALL_ORGANIZATION_UNITS_VL Org, HR_LOCATIONS_ALL_VL Loc, PER_ALL_PEOPLE_F Recruiter, PER_ALL_PEOPLE_F Manager, HR_LOOKUPS Status, HR_ALL_POSITIONS_F_VL posEO, HR_ALL_ORGANIZATION_UNITS_VL Bg, IRC_SEARCH_CRITERIA VSC, HR_LOOKUPS PSA WHERE VAC.vacancy_id = VSC.object_ID(+) AND VSC.object_type(+) = 'VACANCY' and Vac.Job_id = Job.JOB_ID(+) and Vac.Grade_id = Grade.GRADE_ID(+) and Vac.Organization_id = Org.ORGANIZATION_ID(+) and Vac.Location_id = Loc.LOCATION_ID(+) and Vac.Recruiter_id = Recruiter.PERSON_ID(+) and :6 between nvl(Recruiter.EFFECTIVE_START_DATE,:7) and nvl(Recruiter.EFFECTIVE_END_DATE, :8) and Vac.Manager_id = Manager.PERSON_ID(+) and :9 between nvl(Manager.EFFECTIVE_START_DATE,:10) and nvl(Manager.EFFECTIVE_END_DATE,:11) and Status.LOOKUP_TYPE(+) = 'VACANCY_STATUS' and Vac.Status = Status.LOOKUP_CODE(+) AND vac.position_id = posEO.position_id(+) AND :12 between nvl(posEO.EFFECTIVE_START_DATE, :13) AND nvl(posEO.EFFECTIVE_END_DATE, :14) AND VAC.business_group_id = BG.Organization_id and EXISTS (select null from PER_VACANCIES PV where PV.vacancy_id = VAC.vacancy_id) AND (exists (select null from irc_agency_vacancies iav where iav.agency_id = FND_PROFILE.VALUE('IRC_AGENCY_NAME') and iav.vacancy_id = vac.vacancy_id AND :15 between nvl(START_DATE,:16) AND nvl(END_DATE, :17)) or FND_PROFILE.VALUE('IRC_AGENCY_NAME') is null) AND PSA.LOOKUP_TYPE(+) = 'IRC_PROFESSIONAL_AREA' AND VSC.PROFESSIONAL_AREA = PSA.LOOKUP_CODE(+) ORDER BY Vac.NAME*

  • Creating PR in Unapproved Status

    Hi All
    Pl let me know the steps to be followed to create Purchase Requisition in Unapproved Status in Back To Back Order Scenario. Business requirement is to create PR in unapproved status from the SO Line.
    We are on 11.5.10.2 and its urgent.
    Thanks
    Rajeev

    Please refer the below note: Back To Back Process Always Create Approved Purchasing Requisitions (Doc ID 467508.1)
    Goal
    ===
    How does one use the Back to Back Process and have the new requisition be created in status
    INCOMPLETE so that additional lines may be added to the requisition?
    ### Steps to Reproduce Problem ###
    1. Select OM responsibility
    2. Create Sales Order in OM
    3. Book the Sales Order
    4. Run the process "AutoCreate Purchase Requisitions"
    See the field AUTHORIZATION_STATUS in the table PO_REQISITIONS_INTERFACE_ALL
    always is populated with the value "APPROVED",
    5. Select Purchasing Responsibility
    6. Run the process "Requisition Import" with parameter "Initiate Approval after ReqImport" = No
    8. Query requisitions, at this point the requisitions are in status APPROVED.
    Want requisitions in status INCOMPLETE.
    Solution
    =====
    Per standard functionality, the Back to Back Process cannot create new requisition in status
    INCOMPLETE. We create the entry in PO_REQUSITIONS_INTERFACE with AUTHORIZATION_STATUS as approved only.
    As per the present code and functionality, we create the requisition with approved status only.
    Therefore, additional lines may not be added to the requisition.
    AutoCreate Purchase requisition concurrent program or progress order from the sales
    order pad, shall create a requisition for a booked ATO buy item line if there is open
    quantity on the line. This is designed functionality. (By open quantity we mean the
    order qty that is not reserved to a supply).
    If you want to prevent autocreate purchase requisition from processing the line as you
    are already having an existing PO for it you can achieve it in two ways -
    1. Put the line on create supply hold immediately after creating the sales order.
    Autocreate Purchase requisition will not pick such a line. Thereafter, you can
    manually reserve the existing PO to the order line and remove the hold. Once
    the entire quantity on the line is reserved to a supply, it is no longer eligible to
    be processed by autocreate purchase requisition and will not create another PO.
    2. CTO provides a custom hook CTO_CUSTOM_SUPPLY_CHECK_PK. You can
    add logic here to prevent CTO from trying to create supply. Please refer to CTO
    Process Guide - Setup - Custom Check Supply Creation API.
    To locate manual, see
    Oracle Configure to Order Release Notes, Release 12.1.1 (Doc ID 789425.1)
    Then select Oracle Configure to Order Process Guide, Part No. E13692-01, April 2009
    search for manual, open it.
    Hope this helps.
    Regards,
    Paarthy
    Edited by: Paarthy on Mar 16, 2012 5:52 AM

  • Status of document after duplicate in sbo 2007

    Hi,everyone
    I meet a problem in sap business one 2007B.
    When I duplicated a purchase order ,I found its status is "Unapproved", instead of "Open". So are those marketing documents.  Because of it,I can't create a Goods Receipt PO according to that purchase order .

    Hi Li,
    I assume you are involved in the ramp-up of 2007B, since the version is not generally available yet.
    Under Administration -> System Initialisation -> Document Settings -> Per document -> Purchse order, see if the checkbox 'Purchase Order Approved' is ticked. This setting is applicable to all POs.
    If this setting is present in the lower version database but not in the upgraded one, please log a support ticket.
    All the best,
    Kerstin

  • Include the Content Released status flag in default WC data control

    Hi,
    We have integrated custom webcenter portal application with UCM for documents integration. The integration was done using default data control.When we change the document which is getting displayed in the portal from UCM and check it into the system, wokflow gets triggered properly and the content status shows review status. But when we access the document in the portal, at that point of time new document is visible even though the content is still not released from the system.
    Can anyone of you let me know how to include the released status of the content in the default data control so that we can avoid this situation
    Regards,
    Boopathy

    First of all, I think this is more a question to WebCenter Portal, because it is how WebCenter Portal components are written.
    Another thing is, that this is probably 'works as designed' and there might be good reasons for that. Since PS3, WebCenter (Portal) exposes some of UCM's functionality, among them ability to approve items in a workflow. This is the reason why it makes a good sense that items are available. Of course, they should be available only to approvers; also unapproved items should not appear if an item is displayed via Content Presenter (compare to a document published on a website via WCM). If you found such a behaviour, please, report it to MetaLink as it might be a bug.

  • Status in purchase order

    1.Where do i see the workflow for a purchase order.
    2. There are 6 status in purchase order, can someone give me the link or document about the status?
    Regards
    Sudharshan

    1. Workflow for a PO can be seen from the navigation given below.
    Purchasning > Purchase Orders > Purchase Order Summary > Inquire (M) > View Approval through workflow.
    2. Use the Control Documents window to control requisitions and requisition lines as well as purchase orders, purchase order lines, releases, and shipments. For requisitions, the only available actions are Cancel and Finally Close. Only control options appropriate for the selected requisition or purchase order are displayed in the Actions field. The following control actions are available in this window:
    Cancel - If you use on-line requisitions, and you cancel a purchase order you did not receive or pay at all, Purchasing cancels the requisition lines associated with the purchase order if the Cancel Requisitions check box is selected. If the Cancel Requisitions check box is not selected, the requisition lines are not cancelled and are returned to the pool of available requisitions. You can then assign these requisition lines to new purchase orders to fulfill your requestors' needs. See: Defining Control Options.
    If you use on-line requisitions with quantity or amount based line types, and you cancel a partially received purchase order line, Purchasing recreates requisition lines for the remainder of the maximum of the billed or received quantity you have not received. You can assign these requisition lines to a new purchase order line to fulfill the requestor's needs. See: Autocreate Document Options. If you have implemented Oracle Services Procurement and use on-line requisitions with rate or fixed price line types, no requisition lines are recreated.
    If you are using encumbrance or budgetary control, Purchasing automatically creates negative debit entries in your general ledger system to cancel the encumbrance that corresponds to the purchase order header, lines, or shipments you are cancelling, using the action date you specify in Action Date. Purchasing recreates requisition encumbrances for the requisition lines you used to create the purchase order if the Cancel Requisitions check box is not selected. Purchasing uses the distributions from your cancelled purchase order to recreate the encumbrance for your requisition. See: Budgetary Control and Online Funds Checking.
    After you partially or completely cancel a purchase order, you need to inform your supplier of the cancellation. You can communicate purchase orders or releases you partially or completely cancelled. Purchasing automatically inserts a cancellation message on the purchase order, purchase order line, purchase order shipment, or release you cancelled.
    You can source a requisition line from a line in the Prior Purchases region of the Supplier Item Catalog window. (A line in the Prior Purchases region corresponds to a purchase order line.) However, Purchasing does not automatically update the corresponding sourcing information if you cancel a blanket agreement or agreement line with which you source requisition lines. If you cancel a blanket agreement or agreement line, be sure to update the corresponding information in the Requisition Templates or the Sourcing Rules window. See: Defining Requisition Templates. See: Automatic Sourcing.
    Close - You can close at the header, release, line, and shipment levels.
    Close for Invoicing - You can close for invoicing at the header, release, line, and shipment levels. Note that if you close for invoicing a purchase order header that is currently open, Purchasing sets the status of all purchase order shipments to Closed for Invoicing, but the purchase order lines and header remain open. This status will not prevent you from matching an invoice to the purchase order or to the receipt.
    Close for Receiving - You can close for receiving at the header, release, line, and shipment levels. Note that if you close for receiving a purchase order header that is currently open, Purchasing sets the status of all purchase order shipments to Closed for Receiving, but the purchase order lines and header remain open.
    Finally Close - You can final close at the header, release, line, and shipment levels. Purchasing automatically closes fully billed and received purchase orders. However, to prevent further actions on the purchase order, you should use this window to final close purchase orders. Finally Close prevents modifications to the purchase order. Also, if you are using encumbrance or budgetary control, Finally Close automatically creates credit encumbrance journal entries in your general ledger system to reverse the encumbrance that corresponds to the purchase order header, lines, or shipments you are closing, using the action date you specify in Action Date. See: Budgetary Control and Online Funds Checking.
    Freeze - You can freeze only at the header and release level. You freeze a purchase order when you want to prevent any future modifications to the purchase order. When you freeze a purchase order, you can still receive and pay for goods you already ordered. If you want to prevent future receipt or matching invoices against this purchase order, cancel or final close the purchase order instead.
    On Hold - You can place a purchase order on hold only at the header level. This unapproves the purchase order while preventing printing, receiving, invoicing, and future approval until you remove the hold.
    Open - You can open at the header, line, and shipment levels.
    Open for Invoicing - You can reopen for invoicing at the header, line, and shipment level.
    Open for Receiving - You can reopen for receiving at the header, line, and shipment level.
    Release Hold - You can release a hold only at the header level.
    Unfreeze - You can unfreeze only at the header and release levels.

  • PO Status in iProc

    Hi all,
    I would like to know if it is possible for the requestor to only see the PO number in iProc 11.5.10 whenever the PO is approved and not before approved status.
    Thanks,
    Leonie

    Yes - I found a way the other day.
    Go to the Requisition screen in iProc
    Just above the table with the Req details, there should be a link saying Personalize "This table displays a listing of..."
    [If you can't see this personalisation link (or any of them) - see * below]
    When the personalisation strucutre table is displayed, scroll down till you see the heading Switcher : Order (expand all if required) and then within that look for Message Styled Text: (OrderWithoutLink)
    Click the pencil icon to edit, scroll down to the Rendered field and change from Inherit to False at whatever level is required (site, org or responsibility).
    Click Apply and then Return to Application and that should be you done. Click on a Req to view the details and repeat above customisation to hide the unapproved PO from that screen too, if required.
    * If you don't have personalisation access, you need to change profile options in sys admin (or get someone to do it for you)
    In Sys Admin go to Profiles and ensure the Personalize Self-Service Defn and FND: Personalization Region Link Enabled fields are both set to Yes for your user
    Hope this helps
    Edited by: user12267923 on 25-Jan-2011 08:24

  • Get invoice status from back end (validated/ not validated)

    Hi,
    How can i find the invoice status from the back end. I am creating a custom form where in need to populate only validated invoices. Is there any proc. for this ? Was looking around for the proc but unable to find one.
    Regards
    Deepak

    Hi all,
    I have got the proc. ap_utilities_pkg.get_invoice_status
    This proc. takes invoice_id as an input parameter and returns in "UNAPPROVED' if validation or approval fails.
    Regards
    Deepak

  • Unapproved Sales Order Procurement Wizard creates target document

    Production Order Creation through Procurement Wizard
    1. Create a sales order with an item that has a Bill of Material
    In OEC computers
    Customer = "Norm Thompson"
    Item = "S10000" "Server Point 10000"
    2. Set Sales Order to Unapproved ( Logistics Tab -> uncheck approved )
    3. Click the Add Button
    4. Go to last sales order, verify the Sales Order Status is Unapproved
    5. Run Procurement Confirmation Wizard
    6. A production order is created
    Is this correct functionality?
    Is this a bug?
    Seems to me that the correct functionality would to not create procurement documents if the sales order is not approved or have on option on the procurement  wizard to not include unapproved sales orders.
    Has anybody run into this problem? If so, how did you prevent procurement documents from being created?
    Thanks
    Jeff
    Edited by: Jeff Campbell on Mar 2, 2012 7:07 AM

    Hi Saurabh,
    As per your Screen Shot, I think you have Add-on.
    Please stop that Add-on and then check above Scenario.
    Thanks
    Regards::::
    Atul Chakraborty

  • Changing the Customer no for unapproved project

    Dear Dina,
    A new project created with customer A and the project is in unapproved status...at this stage any possibilities to change the customer number to that project...for the same project number...
    or
    we need to end date the existing project and create new 1.
    please advice.
    thanks a lot n advance....

    Hi
    Using the form you could always add customers to the project with zero % of contribution.
    If you have a wrong customer assigned to a project, and you have not allocated funds from that customer agreement to the project, you are in a safe place. If you had allocated fund, enter a negative fund line for the wrong customer agreement, and baseline the funding, so it become zero.
    Now, even when the system does not allow you to update the customer percentage, you can do it directly on the database using TOOLS EXAMINE or SQL. Update the percentage of the wrong customer to zero, and the percentage of the correct customer to 100%. Since this is an intervention behind the forms, you should do it very carfully. Verify you are doing such update while no user is trying to baseline funding or revenue budget, and also that no one is running GDR or GDI on the same time.
    Dina

Maybe you are looking for