PB00 conditon type in PO with document type NB-under what condition?

Hi,
Can anyone tell me under what circumstances PB00 condition type appears in a standard purchase order (doc. type NB) ?
My understanding is condition records in Inforecord & contracts are always PB00,i.e. time dependant.
& condition records in RFQs & Scheduling agreements can be made PB00 or, PBXX (time independant) through SPRO settings.
I thought that condition type in a PO has to always be PBXX ,i.e time independant but when I create this particular PO, condition type PB00 gets populated!
Please advise.
Thanks,
Kaveri

you have worng understanding about the PB00 and PBxx conditon
PB00 will come to PO if you have created info record or if you are creating PO reference to contract, RFQ or SA.
but when you create the PO and there is no info record is created than system will defualt the PBxx conditon becuse the system search first all the access sequence and does not find Pb00 in than it will populate PBXX conditon
you can review in the PO how the system is determine the condition
to do that click on the conditon tab and hit analysis
here the right side you will see conditon record found for PB00 andleft side youwill see from where the system find the conditon by opening the arrow.
If po has PBXx than you want see any access seq on left

Similar Messages

  • SD invoice posted with document type RV ,

    Hi all,
    I try to do incoming payment for SD invoice posted with document type - RV. when i used to do incoming payment by transc code: f-28. An ABAP dun error occurs, stating termination " message type-X".
    Is it possible to do incoming payment for SD invoice from FI. Urgent help needed.
    Regards
    Raj

    Hi,
    Once an Invoice is created in SD, An Accounting document is generated with document type RV. RV Doc. Type shows that the customer is liable to pay the amount.
    While you post the document through f-28, the document type shuld be changed to customer payment.
    It may be one of the reason. So select the docment type customr payment  but not RV and try
    Regards

  • Getting error while processing EDIFACT-D96A-ORDERS.. Agreement not found for trading partners: FromTP HTP, ToTP null with document type ORDERS-D96A-OUTBOUND

    Hi Anuj & All,
        I'm trying to create an outbound scenario with EDIFACT-D96A-ORDERS. A simple SOA composite application polling data from DB and through B2B adapter 'send' option provides data to B2B system.
    Set up two partner profiles like this,
    Host:
    Name: HTP
    EDI Group ID: HTP
    EDI Interchange ID: Interchange Sen
    EDI Interchange ID Qualifier: 01
    Remote:
    Name: RTP
    EDI Group ID: RTP
    EDI Interchange ID: Interchange Rec
    EDI Interchange ID Qualifier: 01
    Other settings are as usual. Delivery channel of generic file created on RTH.
    Now, few documents settings on B2B console are like this,
    D96A-> Interchange tab
    Create UNA: Never
    ORDERS-> Transaction
    Functional Group Identifier Code: ORDERS
    Controlling Agency: UN
    - other properties are unchanged.
    On SOA side, the bpel invoke activity which calls B2B adapter has following properties:
    <invoke name="InvokeOrders"
      inputVariable="InvokeOrders_send_InputVariable"
      partnerLink="D96A.ORDERS" portType="ns2:send_ptt"
      operation="send" bpelx:invokeAsDetail="no">
    <bpelx:inputProperty name="b2b.toTradingPartnerIdType"
        expression="'NAME'"/>
    <bpelx:inputProperty name="b2b.toTradingPartnerId"
        expression="'RTP'"/>
    <bpelx:inputProperty name="b2b.messageType" expression="1"/>
    <bpelx:inputProperty name="b2b.messageId" variable="messageID"/>
    <bpelx:inputProperty name="b2b.fromTradingPartnerIdType"
        expression="'NAME'"/>
    <bpelx:inputProperty name="b2b.fromTradingPartnerId"
        expression="'HTP'"/>
    <bpelx:inputProperty name="b2b.documentTypeName"
        expression="'ORDERS'"/>
    <bpelx:inputProperty name="b2b.documentProtocolVersion"
        expression="'D96A'"/>
    <bpelx:inputProperty name="b2b.documentProtocolName"
        expression="'EDIFACT'"/>
    <bpelx:inputProperty name="b2b.documentDefinitionName"
        expression="'ORDERS_def'"/>
    <bpelx:inputProperty name="b2b.conversationId"
        variable="ConversationID"/>
    </invoke>
    The error I'm getting on B2B Console->Reports->Business Message, while running this is,
    Error Code B2B-50547
    Error Description Machine Info: (htp01310-vm01.htp.com) Description: Agreement not found for trading partners: FromTP HTP, ToTP null with document type ORDERS-D96A-OUTBOUND.
    Error Level ERROR_LEVEL_COLLABORATION
    Error Severity ERROR
    Error Text Agreement not found for trading partners: FromTP HTP, ToTP null with document type ORDERS-D96A-OUTBOUND.
    Note: On Manage Deployment Tab I've checked the agreement is in active state.
    -- Business Message (Result):--
    State: MSG_ERROR
    Document Type: ORDERS
    Agreement: <blank>
    Sender: HTP
    Receiver: <blank>
    -- Application Message (Result):--
    Sender Id Type: NAME
    Sender Value: TCS
    Receiver Id Type: NAME
    Receiver Value: ORCL
    Document Type: ORDERS
    Document Definition: ORDERS_def
    Document Protocol Name: EDIFACT
    Document Protocol Version: D96A
    Direction: OUTBOUND
    State: MSG_COMPLETE
    - Can anybody please shoot some pointer on how to resolve this? Please let me know if you need further configuration details which I've not mentioned here.
    Regards,
    - @bhijit

    Hi Mariusz,
        Thanks for your reply. Yes I think so, probably you're right. But finest trace level doesn't give much clues on "wrong mapped" data. Anyway, here is the detail log. Please don't forget to point out if you find something interesting.
    #### <Error> <oracle.soa.b2b.engine> <htp01310-vm01.htp.com> <soa_server1> <Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms
    > <<anonymous>> <BEA1-0D3F5ABAC0B2E50C6CCB> <449b4b64fa2729cc:59737e36:146f08831ee:-8000-0000000000127da6> <1404379704092> <BEA-000000> <Error -:  B2B-50547:  Agreement not found for trading partners: FromTP HTP, ToTP null with document type ORDERS-D96A-OUTBOUND.
      at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:887)
      at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:415)
      at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:465)
      at oracle.tip.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:224)
      at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1555)
      at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:819)
      at oracle.tip.b2b.engine.Engine.outgoingContinueProcess(Engine.java:4100)
      at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3921)
      at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3309)
      at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:637)
      at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
      at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
      at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
      at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Error -:  B2B-50547:  Agreement not found for trading partners: FromTP HTP, ToTP null with document type ORDERS-D96A-OUTBOUND.
      at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:887)
      at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:415)
      at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:465)
      at oracle.tip.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:224)
      at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1555)
      at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:819)
      at oracle.tip.b2b.engine.Engine.outgoingContinueProcess(Engine.java:4100)
      at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3921)
      at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3309)
      at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:637)
      at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
      at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
      at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
      at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    >
    #### <Error> <oracle.soa.b2b.engine> <htp01310-vm01.htp.com> <soa_server1> <Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms
    > <<anonymous>> <BEA1-0D3F5ABAC0B2E50C6CCB> <449b4b64fa2729cc:59737e36:146f08831ee:-8000-0000000000127da6> <1404379704569> <BEA-000000> <Error -:  B2B-50547:  Agreement not found for trading partners: FromTP HTP, ToTP null with document type ORDERS-D96A-OUTBOUND.
      at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:887)
      at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:415)
      at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:465)
      at oracle.tip.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:224)
      at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1555)
      at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:819)
      at oracle.tip.b2b.engine.Engine.outgoingContinueProcess(Engine.java:4100)
      at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3921)
      at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3309)
      at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:637)
      at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
      at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
      at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
      at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Error -:  B2B-50547:  Agreement not found for trading partners: FromTP HTP, ToTP null with document type ORDERS-D96A-OUTBOUND.
      at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:887)
      at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:415)
      at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:465)
      at oracle.tip.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:224)
      at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1555)
      at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:819)
      at oracle.tip.b2b.engine.Engine.outgoingContinueProcess(Engine.java:4100)
      at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3921)
      at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3309)
      at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:637)
      at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
      at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
      at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
      at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    >
    Rgds,
    - Abhijit
    P.S. - Can you please check what is the value of "Functional Group Identifier Code" for D96A ORDERS.

  • "Goods Movement type not possiable with mvmt type 261"

    Dear All,
    I am doing 541 movement with Service order combination, i have found following error,
    "Goods Movement type not possiable with mvmt type 261"
    Can you help me for this error.
    -Reards,
    Sunil

    Getting errors while using PI_GOODSMVT_CREATE' with 561+K

  • Multiple Output types to existing Billing document type

    Dear Gurus
    I have a requirement. I need to assign multiple output types to existing Billing document type. But there is only one output type/procedure can be assigned in the Billing document type. My client wants another print output format for the same document type. I can get a new smart form created and assigned to the output type.
    But wher would i assign that to the billing doc type? Or is there any other way out?
    Can u pl help me out?
    Thanks in advance...
    regards
    Gansub

    Hi,
      Create a new output type and assign the new smartform and program and add this new output type in the existing procedure assigned to the billing document type.Maintain the condition record inVV31 for this new output type.So both existing and new output type will be available in the billing doucment to take the print out.
    Regards,
    Gopal.

  • Problem with document type on WF for parking document

    Hello
    Iu2019m actually working on  the SAP workflow dealing  with the FIPP object and  the event u201Ccreatedu201D (FI park document transaction (FV60)).
    The problem is that the WF is launched for all document types wich is not the need of the customer. Iu2019m looking for a solution to launch the WF for some specific document types.
    Iu2019ve already tried to use  the workflow variant, approval groups, paths and procedure with no success. (SPRO -> financial accouting-> accounts receivable and accounts payable -> business transaction -> incoming credit invoice memo -> make and check setting for document parking)
    Thank you for help.
    SL

    Here is the solution I have  eventually found :
    1-      Application of the OSS note 559276 which enables the customizing of the workflow variant (the transaction OBWD becomes here effective)
    2-     Assignment of the documents types, workflow variants and release approval groups with the transaction OBWD.
    Therefore, the document types that are not defined in the transaction OBWD will not require validation (no workflow will be launched).
    SL

  • Problem in FEBA / FB05 with document type

    Hi:
    I have a requirement. My users need the possibiliyu to choose the document type when they use FEBA TX. When FEBA is used, it calls FB05 TX, but you cannot choose the document class. We have defined a posting rule that uses in only a document type in this case, but when we use FEBA we cannot change document type. We need the possibility to choose several document types. I tried with OB28 Validation of Accounting Documents, but doesn`t work.
    Please, do
    you have any idea, user exit or solution for this problem? Release 4.6.C
    Thanks in advance.
    Best regards

    the structure arc_buffer has following fields
    RCSZK
    RNAME
    CHECKSUM
    FLAGS
    SEGMENT
    so in the routine
    PERFORM read_file USING handle_tab_wa-offset record_len
    CHANGING arc_buffer(record_len)  "here just use it like arc_buffer-<field_name>(record_len)
    error_handling
    p_message.
    or before calling the perform statement
    data:lv_string type string.
    call method cl_abap_container_utilities=>fill_container_c
    exporting
    im_value = arc_buffer
    importing
    ex_container = lv_string
    exceptions
    illegal_parameter_type = 1
    others = 2.
    PERFORM read_file USING handle_tab_wa-offset record_len
    CHANGING lv_string(record_len)  "here just use it like arc_buffer-<field_name>(record_len)
    error_handling
    p_message.

  • Authorisation combined with document type, activity and status

    I want to create a role for a user who is only allowed to create and change document type ZDI  in status IW .
    Which object authorization can provided this check ?
    The object authorization C_DRAW_TCD  control only the activity (create/modify) and the document type (ZDI).
    The object authorization C_DRAW_STA control only  the document type (ZDI) and the status of the document (IW).
    But I need the combination of the both authorization. Does a possibility exist in standard to do it without create a client new authorisation?
    Thanks in advance for your help.
    Amande

    Thanks for your response.
    But it doesn't works as I want.
    The object authorisation C_DRAW_TCS  is checked before the save but not after save with the changed values.
    for example :
    the user has the following authorizations in the modification role:
      C_DRAW_TCS  activity 02 document type ZDI  document status IW 
      C_DRAW_TCD document type ZDI  activity 02
      C_DRAW_STA document type ZDI status IW
    The user has also the autorisation C_DRAW_STA document type ZDI status FI  in the display role
    With this configuration the user can modify the document ZDI in status IW and change the status into FI . I don't want that the user can change the status into FI. Does exist a possibility to avoid this?
    Of course, after storing this change of the status , the user can't access to the document ZDI with status FI.
    SAP doesn't check the authorization C_DRAW_TCS  activity 02 document type ZDI  document status FI  after status change.
    Thanks in advance
    Amande

  • Flexupload Method for Manual Elimination - Flexupload with Document Type

    Hi All
    My Customer has Multiple Lines of Manual Elimination Entry every Month. I was wondering is there any way to Process Flexupload Method - DOCUMENT TYPES in SEM-BCS? as I 'd tried in *Data Collections*, It wont pull up Posting Level-20 Document Type
    Data Collections Only from Posting Level 00 to 10
    Appreciated Your Thoughts and Help
    Regards
    Ramana

    Hi,
    did I understand that right: You want to upload eliminations?
    In SEM-BCS you can only upload either master data or reporting data.
    For reporting data you upload data on items with subassignments (e.g. movement type).
    If your customer a bundle of some eliminations that are always the same, then why don't you a manual posting and customize it with a document type without automatic inversion? These postings will appear in every following year after posting. This is available for all posting levels (01-30).
    You could, of course, use a "strange way" and customize a flex upload with "reported financial data" and create a upload file with the special data for those entries.
    BR
    Benjamin Maier

  • Problem with document type in ME51N

    Hi all,
    ME51N transaction will pickup NB document type by default. We can change the default document type by using personal settings in ME51N. But, can we restrict document type using ABAP development irrespective of default settings. Suppose NB is default doc type. If we open ME51N, some other doc type should come other than NB. Is it possible by ABAP development. Its very urgent. Please help me in  this.
    Thanks in Advance,
    Siva Sankar.

    Siva Sankar
    You may use Field Exit to do this enhancement. You can create fieldexit from report RSMODPRF.
    In order to use field exit check/activate Profile Parameter abap/fieldexit using t code RZ11.
    Thanks & regards
    Amol Lohade

  • Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

    Hi Friends,
    I have a issue to fix. The issue is releated to PR.
    There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
    I have to retrigger the release strategy for all the affected PR's.
    The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
    Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
    Regards,
    Manjunath K

    Hi,
    Refer the discussion to triggers release again on release code addition/change in release strategy.
    release code is changed on PR release strategy - old PR can´t be approved
    Regards,
    Biju K

  • Change the condition type based on sales document type

    Dear ALL,
    I have created a condition Zxxx which is a fixed calculation type for the documents created by the upload from external tool to SAP.  I created this condition because external tool is using a 15 place decimal which SAP doesn't allow and if the normal condition type Zyyy is used SAP calculates once in SAP and there are rounding issues.  What the Zxxx condition type does is accept whatever value is sent up from external tool to SAP, regardless of the quantity.  The problem is that whenever they create a credit with reference, in SAP and they want to do a partial credit, the Zxxx doesn't take the partial quantity into consideration and doesn't change the value. 
    Is there a way to force SAP to change the condition type from Zxxx to Zyyy based on sales document type without recalculating the whole document because that would again, cause rounding issues.  We would need to have the calculation done only on quantities changed in the credit memo request .
    please advice me. your inputs are highly appreciated.
    TIA
    KOGI

    Dear ALL,
    someone please help me with this issue. your inputs are higly helpful.
    TIA
    KOGI

  • Two different billing document types for 1 sales document type.

    Hi Gurus,
    I have a requirement , wherein our client is having counter  sale.
    He is using one sales doc type , and while creating a order , he is manually adding payment terms.
    Requirement is , if the payment terms are cash, billing doc type created later on should be one , else during credit sales , billing document type should be different.
    As per my understanding this is not possible.
    Want to know if anyone has some different thought on this.
    Thanks in advance
    Nilesh.

    Dear Nilesh,
    There two options you can look in to
    One option is
    1.You can define different sales document types for cash and credit.
    2. You can define two different billing documents.
    3.Do the copy control settings for each combination
    Cash sales order >Delivery>Cash invoice
    Credit sales order >Delivery>Credit invoice
    Second option is
    1. You can maintain single sales document for both the processes.
    2.Define two different billing types then do the copy control settings for both billing types.
    But in this option user need to select the billing type manually based on the process while creating billing document.
    I hope this will help you,
    Regards,
    Murali.

  • Order type field for PO/Document type field for PR

    Hi Everybody
    a) In Purchase Order creation screen (ME21)-for order type field -NB(standard order) is coming as default-How to make it blank(since we are using plantwise PO NOs)
    b)In purchase requisition screation screen(ME51)also Document type-NB(standard order) is coming as default-How to make it blank(since we are using plantwise Purchase requisitions)
    Thanks in advance
    Joseph David

    Simple,In order of ME21/ME51,Press F4,Select Required order/requistion type,Add it to Favourite list
    or else
    Create a transaction variant for ME21 & ME51 using t.code SDH0.
    Transaction Variant - A Step by Step Guide for Creation,Check below link,
    http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation
    Edited by: Jeyakanthan A on Apr 2, 2010 5:42 PM

  • SD document type link to FI document type

    Hi
    I have many document types for credit notes in SD.  When the accounting document is created they have the same doc type DG.   Our requirement is to have different FI document type for each of the SD document type.
    Where is the config to link this.
    Thanks Ashok

    Hi,
    The document type is linked to the billing document type config.
    Regards,

Maybe you are looking for