Settlement of WBS with Partially Released status

Hi colleagues,
We are encountering problems during our settlement to AUC. Although the settlement rule is maintained, the system does not allow us to post the settlement to a WBS with "PREL" (partially released) status. Is this really the standard of the system? When can we release the WBS?
Thank you.

Ask your FICO consultants to create a separate Asset class for AUCs.
They can maintain such class in OAOA, where ask them to maintain status of Auc as Investment Measure.
Now you can use this class in OITA - Investment Profile.
And assign this Investment Profile to Project Profile in OPSA.
Assign this Profile to capital project.
Now all your assets which are AUC stage will come to this asset class.
You can create completed asset in the other class by full settlement.
Rewards for helpful answer.
Thanks,
RIYA

Similar Messages

  • ENCUMBRANCE ENTRIES FOR REQUISITION WITH PARTIAL RESERVE STATUS?

    Hi,
    On 11.5.10.2 in Production:
    When a Purchase Requisition (PR) is created with 2 distributions with 2
    different budget a/c and one account having sufficient funds and other one
    not having funds,
    Now reserved he PR which was showing the Budgetary control exception -
    Line 1 Distribution 1 fails funds check
    Line 1 Distribution 2 passes funds check
    In this case will that document is eligible to forward to the next manager for approval or will the document remains in “Incomplete” status.
    If that document is forward to the next manager for approval what was the reason behind that…?
    Please let me know..
    Regards,
    Kv.
    Edited by: Peter.Kv on Oct 25, 2009 9:34 PM

    Hi all,
    the problem was that the relation between plant and product was somehow mixed up. We created it new and now we can process the mesasges.
    But i have one more questions, which Monitoring Transactions i have for SRM (Abap/Portal)? When I was in Debug Mode i saw error Messages like:
    A     /SAPSRM/CH_SOA_MSG     84     Purchasing group for follow-on document missing
    A     BBP_PD     245     Purchasing group for follow-on document missing
    A     BBP_PD     246     Purchasing organization for follow-on document missing
    A     BBP_PD     249     Document type for determined backend system missing
    E     BBP_PC     13     No default value is defined
    E     BBP_PC     22     No tax data maintained
    E     BBP_PD     276     Back-end data could not be read
    E     BBP_PD     358     Select a location that is assigned to the plant chosen
    E     BBP_TAX     1     Tax code could not be determined
    E     BBP_TAX     13     Not possible to calculate tax
    But i only saw that in the monitoring? These Errors can happy every time and i need to see them.... can you please tell me, where i can have a look?

  • PO Release status with date

    Hi Guys,
                 I have a requirement where in I need to list out the POs with the Release status based on
                 date range. Any pointers on this is appreciated.
    Thanks.
    Rgds,
    Senthil GR

    hi
    go to me2n then select the date range and then press shift+F4 (dynamic selection )here in header u can select the release indicator and dates
    regards
    kunal
    award if helpful

  • Issue with PO release (multi level approval)

    Hi,
    Need help regarding PO release. I am working with 4 level  approval process.
    Information:
    it is sequential release as I can see in workflow log, a new workflow gets generated for next level only after previous level executes the workitem.
    Facing following issue at 2nd Level :
    Level 2 releases item and it goes to Level 3, but workitem doesn’t disappear from inbox.Once Level 3 releases item, an acceptance mail goes to Level 2. But along with the mail, updated workitem (i.e. showing release by 3rd level) also appears in inbox of Level2. Now two work items appear in Level2 Inbox.
    In Workflow Log, this is how its behaving:
    WORKFLOW STARTED-->
    1st WF appears in WF log.
    Level 1 releases WI ->
    2nd workflow appears in WF log +
    1st workflow with (in process status)
    Level 2 releases WI ->
    3rd WF appears +
    2nd workflow with (in process status) +
    1st workflow with (in process status)
    Level 3 releases WI ->
    3rd WF appears +
    2nd workflow with (in process status) +
    1st workflow with (in process status)
    ISSUE: As soon as Level 3 sends back acceptance to Level 2, updated WI item appears( i.e. with latest release status which in this case is: released by level1, Level2 and Level3) along with the mail.
    Level 4 releases WI ->
    4th WF appears +
    3rd WF appears (in process status) +
    2nd workflow with (in process status) +
    1st workflow with (STATUS COMPLETED)
    ISSUE: As soon as Level 4 sends back acceptance to Level 2, updated WI item appears( i.e. with latest release status which in this case is: released by level1, Level2, Level3 and Level 4) along with the mail.
    Result:
    PO gets released.
    In workflow log 2nd, 3rd and 4th workflow appear with IN PROCESS STATUS. All of them show process stopped at LEVEL2.

    Hi Kjetil,
    Release strategy is being used. Configuration for release strategy is given as following.
    RGroup Rcode   Workflow     Agent
    Z6          R1         1                Blank
    Z6          R1             1                Blank
    Z6          R1             1                Blank
    Z6          R1             1                Blank
    Release is sequential.
    For column 'Agent' mentioning position or User is not really useful because we are getting agents through Z table. Reason is: current org structure supports 1 position with multiple users from same department. In our scenario we need to find initiators department then find relevant approval levels for that departemnt. So I cannot mention any position in 'Agent' Column as release code will be locked against one position and one departetment.
    Agents picked through Z table. Table has fields  Agent/ UserID , level, department.
    Logic to pick agents( Object and method created ): 
      When workflow starts, it finds department of the initiator.
      For that department-> find approval levels available(L1, L2,  L3).
      For these levels -> Find Agent mentioned for that level.
      Onece Agents are found for all levels -> Pass them to WF  container.
      In task activity, These agents are passed back to the rule and  the task comes to know which agent it should go to.
    Result : Four workflows start in sequence. When last level releases, only 1st workflow shows COMPLETED status. Rest three hang at level 2. If I see Me29N , release for that item is shown completed. To me it seems triggering of only first workflow is enough for release. Is there any way I can avoid trigerring of other three workflows?
    Edited by: User112 User112 on Jan 25, 2008 6:30 AM
    Edited by: User112 User112 on Jan 25, 2008 6:31 AM

  • To show the release status of the transport request

    Hello Experts,
    I am having a requirement like the following:
    I need to list the transports along with the release status of the transport request in a View.
    Release status means that transport request imported into Development system, Quality system and Production system.
    Which table will hold this information?
    I have checked with E070. But i dont know how to find in that. Or any other table is there to do this?
    Thanks and Best Regards,
    Suresh

    Hello Kalyan,
    I dont know how to find my request in TMSBUFTXT.
    For example i am having a TR now in Dev system: XXX45678.
    If i have imported it to Quality system, then how to find this entry?
    Or if i have imported it to Production system, then how could i find that the TR XXX45678 is now in Production system.
    Since i am creating a View, i need the information that in which Database Table this entry will be stored.
    I dont want Function module name.
    Best Regards,
    Suresh

  • How to set the overall credit status as "partial release" on SO header?

    Hey guys,
    Do you have any idea on how did the overall credit status become "partial release" on sales order header level?
    Because as my understanding in SAP, i am not sure whether there is a way to partial release a sales order with multiple item lines.
    Jasper

    Hi balajia,
    after seeing your description i have gone to VKM4.
    i have executed OVER ALL CREDIT STATUS with A.
    then i am able to see one sales order with OVCS - 'A'.
    then i have given OVCS as 'B' & also "C' -  i am not able to see any sales order OVCS as B & C.
    that means here there are options to use if OVCS in sales order status is B or C as it has executed for A.
    so,
    some where in sales order program it is hard coded i think so - i am saying this because there is a link between sales order header:
    Delivery status      Not delivered
    Credit status        Not performed
    Overall blkd status  Blocked
    so if it is hard coded with B and C also you can use these options in VKM4.
    that's is what my R & D on this says.
    regadrs,
    balajia

  • Digital Signature only Release Status with 3(Approver) Signer

    Hello SDN Folks
    I have done all the basic settings for Digital Signature which is sawn in following link
    http://wiki.sdn.sap.com/wiki/display/PLM/Digitalsignaturein+DMS
    it is work  fine with 1 RE (Release) status and 1 Signer
    We have in process to implement Digital Signature with only two Status
    our scenario is
    Document Creator  Create Document With Status CR
    Document Approver Approve Document With Status RE
    now we have scenario that For 1 Document we have 3 Approver and 3 approver must digitally sign on DIR
    our status is
    only   CR(create)---->RE(release)
    so how i can attached 3 digital signer  with only 1 RE(Release) Status
    is it possible to go with 3 digital signer with only 1 RE (Release) Status ????
    Regards
    Tushar Dave

    Hi Tushar,
    Your requirement of utilizing 3 different approvers for a single 'Release' status in a document type/s can be addressed via the approach proposed below:
    1.Define 3 individual authorization groups
    2.Define 3 individual signatures
    3.Define a common signature strategy
    4.Assign the above 3 individual signatures to the common signature strategy
    5.Define the signature sequence(the order in which the 3 approvers must approve)
    6.Define users and restrictions(signature assigned to relevant approvers/users)
    7.For the document type in question for the 'Release' status,assign the above signature strategy and test.
    For more detailed information on using digital signature effectively,refer the below link
    http://help.sap.com/saphelp_470/helpdata/en/9f/857f3a1c7b11d294d200a0c92f024a/frameset.htm
    Regards,
    Pradeepkumar Haragoldavar

  • Condition Tables with Release status

    When we create condition tables, we have the option of creating them with release status or without release status. What is the difference? What is release status?
    Thanks,
    Venkat

    hi,
    The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
    Release status has the following characteristics:
    no entry: released
    A: blocked
    B: released for price simulation
    C: released for price simulation and planning
    The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
    Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
    When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
    A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
    The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
    If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
    The release status of conditions in an agreement can only be changed, if
    the condition record has release status in the key
    the agreement has the release status released
    Otherwise the condition record always has the release status of the agreement.
    The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
    If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
    The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
    source : Library.
    regards

  • Settling WBS with Billing element indicator

    Hi Experts,
    I'm trying to settling a Project that contains WBS with 'billing element' indicator marked and others not.
    When I executed CJ88 to settle WBS to CO-PA, only settled wbs without 'billing element' indicator marked.
    Could you indicate me why WBS with 'billing element' indicator marked doesn't settle to CO-PA, is there something special for those WBS ?
    Thanks in advance,
    José Luis
    Edited by: José Luis  Rodríguez on May 4, 2011 2:15 AM

    Hi
    1 .First step is we need to run T: code: CJB2 to generate settlement rule,  if at all settlement profile is not assigned to your project profile and settlement rule is derived from settlement strategy define for the rule assigned in Project profile.,
    2. Once you run step one, it will assign the settlement rule to the WBS with billing element as well it will assign result analysis key into the WBS with billing element (if att alll RA key is not defined in Project profile).
    3. Now Run RA in tcode: KKA2 and save the results. exceute tcode CJIF to see the project results.
    4. Now run the settlement in CJ88, you will see that the costs are settled to PSG. this you can verify in costelemnt report also.
    thanks
    regards
    kishore

  • Project setup, WBS element mgmt, user status, settlement

    What is Project setup, WBS element mgmt, user status and settlement

    If you are after the definitions, the simplest way would be to go to SAP Help.
    If you're after the transaction code, it's CJ20N which is the Project Builder screen.

  • Import Production orders with released status

    We are using DTW to import production orders. It allows to import as "planned" status only and not as as "released status". We have hundreds of production orders per day and its a pain to update each production order to "released" status so that it can be available for reciepts from production and thereafter after recieving the items, changing each and every production order to "closed". Please advice

    Hi Mohamed,
    please use the following for the production order status in the template.                                                                               
    (1)Planned   :-> boposPlanned                                              
    (2)Released  :-> boposReleased                                             
    (3)Closed    :-> boposClosed                                               
    (4)Cancelled :-> boposCancelled                                                                               
    Please refer to the SDK DI help file for the details information.          
    hope it helps,
    Regards,
    Ladislav
    SAP Business One Forum Team

  • Settle PREL WBS element to AUC

    Dear,
    In certain cases customer wants to settle partially released WBS elements to fixed assets under construction.
    Is this possible?
    Cuurently I am having an error when settling ("System status Created is active"). However when I check the business process 'Actual Settlement" for the PREL WBS element it is stated to be active (green alert).
    rgds,
    bert

    This is standard behaviour of system as I understand.  In WBS system status hierarchy is like as below.
    CRTD->PREL>REL>TECO-->CLSD.  System set PREL when below level WBS 1.1 is REL, So, indirectly on 1 lEvel WBS will have both status active at same time i.e PREL and CRTD. So, Eventhough actual settlement is green in PREL but it is blocked by CRTD status.
    However, for confirmation you can alwalys check in SE38 CNSTATUS Report which disply you inconsistancy in System status.
    If someone have other openion / view please share. Interesting question !
    With Regards
    Nitin P.

  • Settling the WBS element costs to an AuC

    Please Explain the procedure for settling the WBS element costs to an AuC & then to asset?

    Hi,
    Please follow the below sequence of steps for this:
    1) For WBS element where the asset has to be created, AUC willbe created automatically when the WBS element is in release status to get this investment profile should be assigned to WBS element in Control Tab
    2) You can see in the system status show as AUC to see the AUC number follow the path
        EDIT-> WBS element -> Investment program--> Asset under Construction where you can see the AUC which is created automatically
    3) Once the above two steps are through, for settlement to AuC goto transaction CJ88 give the WBS element number select the processing type as partial captalization and execute all the costs pertaining to that. WBS elements will be automatically settled to the AUC which is created for that WBS element
    Thanks,
    Prithwiraj.

  • Issue in creation of level 2 WBS for level 1  WBS which is released

    Hello All,
    I am trying to create a level 2 WBS for a alrealy created level 1 WBS using BAPI_BUS2054_CHANGE_MULTI .If the level 1 WBS is not released then level 2 WBS gets created .However if the level 1 is released then level 2 WBS doesnt gets created and i get error ' User status INIT is active (WBS #1) '
    Using T-code CJ20n i am able to create level 2 WBS for released level 1 WBS .

    Hi;
    Do you fill WBS_LEFT, WBS_UP fields for IT_WBS_ELEMENT / IT_UPDATE_WBS_ELEMENT tables.
    Hierarchy is very important for between WBS.
    May help below similar link:
    Re: Create Whole Project with BAPI_PROJECT_MAINTAIN
    Best regards.

  • No Purchase order to be create if WBS is not released

    Hi,
    We are using the PS system and we create a purchase order with account assignment Q, and we enter the WBS in to the purchase order.
    Now the requirement is if WBS is not release system should stop to create a PO. System should allow to create a PO if wbs is fully released.
    Pl advise how to do this.
    Thanks,
    Samir Bhatt

    Please go through CJ02-Edit-Status-Lock fictionally.
    It will not allow you to create a PO if the WBS is under released and locked. Hope this functionality guide/help you...
    Regards
    Vikrant

Maybe you are looking for