Conditional Breaks on subnodes/item level

Hello experts,
We have a requirement for a new Adobe Form, which has a header table and an item table. We have to print multiple documents in 1 printout.
Our Adobe Form context layout is as follows:
- Context node for the Header (1 record for each document)
     - Subnode with the item information ( WHERE conditions are set to the specific document key, so we only have the relevant items of the document in the loop )
We have added a Pagination -> Conditional Break based on the header table key, to trigger a new page break for each document.
But we have a 2nd requirement where we need to trigger a 2nd conditional break based on an item partner difference.
This means we would have to add a conditional break, on the subnode which contains all the item information.
In Adobe Forms, according to our finds, it does not seem possible to trigger a condition break in a subnode/item table, is this correct?
Is it nescecary to bring all the conditional break fields to the header table?
The requirement wants this layout:
- Document 1
     - ITEM PARTNER A
          - Item 1 partner A
          - Item 2 partner A
     ( TRIGGER ANOTHER BREAK for new Item Partner display ) <- The issue
     - ITEM PARTNER B
          - Item 3 partner B
( PAGE BREAK TRIGGERED ) <- OK
- Document 2
We were wondering what the most proper/clean/best practice way is, to achieve this requirement.
( without having to duplicate records on the header table, by means of moving the required field from the item table to the header table )
Thx
Kind regards,
Wouter

Hi Wouter,
Thanks for your response yes its not possible to achive this in nested table. I achieved my output using below logic by duplicating records and using Java script..
http://scn.sap.com/thread/3702677
Regards,
Manu

Similar Messages

  • Same condition type on header and item level = printing problem

    Hi
    I have a customer using some condition types on both item level and header level in quotations, orders, invoices ...
    In the pricing procedures it is customized (V_T683S-DRUKZ) that the conditions must be printed on header level (that is at the bottom of the documents).
    My job is to make the Smartform to print the documents, and I want it of course to be as close to SAP standard as possible.
    SAP standard will print these conditions on header level even if the conditions are at item level, but my customer wants the conditions created on header level to be printed on header level and conditions created on item level to be printed on item level.
    I'm no pricing expert, so my question is:
    Will it be fair if I tell the customer that using the same condition types on header and item level is bad practices - or at least bad karma?
    Best regards
    Thomas Madsen Nielsen

    Hi Shiva Ram and Madhu
    I have no problem understanding header vs. item conditions, so I really don't see anything in oss note 876617, that is relevant in this case.
    Madhu - I do not agree that everything is fine. My issue is that I want to stick as closely to SAP standard customizing as possible. In SAP standard customizing of a condition type you can use the flag V_T683S-DRUKZ to determine if the condition should be printed on header OR item level - you can not choose both header AND item level.
    I have a SAP standard smartform using two functions modules for reading header and item conditions. RV_PRICE_PRINT_ITEM and RV_PRICE_PRINT_HEAD. These function modules are based on the DRUKZ customizing flag and a condition marked for printing on header level will be supplied by RV_PRICE_PRINT_HEAD even when the condition is on item level.
    My point is: SAP standard customizing does not support printing of same condition on both header and item level. I can of course write tons of code to work around this problem, but that would be bad practices

  • Invoice Item level break up for GL accounts

    I want to designe an Audit report where in the report should display item level revenue / Tax / Insurance posted in each GL Account.
    In other words, when the Accounting document against an invoice, it gives the entire value of invoice posted in respective GL accounts. I need to have a break up at item level.
    From SD point of view, the Account determination procedure logic could be incorporated but it may creata performance issue in system as the report may be run for a years period.
    Is there any other logic / table reference?
    The matter is urgent.........

    Try S_ALR_87012291 - Line Item Journal . It is SAP standard and gives the details of GL postings. Enter your invoice and have a look.
    The tables are BKPF ( Header ) and BSEG ( line item ).
    pls assign pts top say thanks.

  • How to derive amount posted in GL account at invoice item level.

    I want to designe an Audit report where in the report should display item level revenue / Tax / Insurance posted in each GL Account.
    In other words, when the Accounting document against an invoice, it gives the entire value of invoice posted in respective GL accounts. I need to have a break up at item level.
    From SD point of view, the Account determination procedure logic could be incorporated but it may creata performance issue in system as the report may be run for a years period.
    Is there any other logic / table reference?
    The matter is urgent.........

    Try S_ALR_87012291 - Line Item Journal .
    pls assign pts to say thanks.

  • Very Important - PR00 Display at line item Level

    Hii Guys,
                 Iam working on a upgrade project & i am facing with the below problem.
    In 4.5b when i create an order (va01), the condition type(PR00) displyed at line item level was in change mode. In case if i want to change it to PN00 i could change it manually. But after the upgrade in ECC 6.0 when i try to do that, iam unable to change as it is in display mode.
    I understand that this field gets populated from pricing procedure determination. Ex: 100010011(sorgDCDVCPPDP)- RVAA01 + PR00 Now by default PR00 will appear in double line entry while creating the order.
    In 4.5b system, I can manually change it to PN00 or any other condition which is maintained in pricing procedure & has valid condition condition records mainatied.
    This iam unable to do it in ECC 6.0 system. As the condition type at line item level is in display mode(we can't change it)
    Experts please throw some light...your help would be highly appreciated.
    Thanks,
    Venkat

    Dear Venkat
    In Standard SAP,  we cannot change PR00 manually in sale order.  However, if you want to change, go to <b>V/06</b>, select PR00.  Here under the tab "<b>Changes which can be made</b>", you can see a field "<b>Manual entries</b>", in which "<b>D</b>" would be there in normal course.  Change it to "<b>C</b>" and save.
    Also go to <b>V/08</b> and untick the box "<b>Mdt</b>" against PR00.
    Thanks
    G. Lakshmipathi

  • Double PR00 condition at item level in the IC

    Hello SAP Gurus,
    I need your help with this issue.
    Scenario: I enter the Interaction Center UI and start creating a sales order with "MXN" as the currency at header level, I enter a product in "USD" and price is not calculated automatically and has to be enter manually.
    When going into the item details two identical price conditions appear:
    PR00 - ....... - USD (blank)
    PR00 - 1.34 - USD (the price I entered at header level)
    I tried to get rid-off one but ít wont let me,a messages is generated: "Cannot erase condition, it´s mandatory".
    I´ve also tried matching the header and item level currency but the same thing happens; the price is enter manually and two PR00 conditions are created.
    This cannot be left like this since it generates errors at the invoicing stage.
    Your help will be trully appreciated.
    Thanks.
    May
    PS.  I am working in the Interaction Center UI / ERP Order / CRM 7.0

    Found the reason and solution for this error in my situation, which has to do with how the prices are assigned to the material.
    The prices for the materials are maintain in a List of Prices per volume uploaded in ECC.  This list has serveral volumen scales, and each scale has a different price (Logic: as the volume increases, the price decreases).  The issue here is that the initial scale for some materials was to set to high and sales orders were being created with quantities under that scale, as a consequence the price was not calculated automatically because it didnt fell under any scale and the by manually entering the PR00 condition, somehow it would create an extra could not be erase.
    Example:
    - Material: ABCD
    - List of Prices per volume for ABCD: Scale 1) 1000KG - 1499KG -> 2.50 USD  /  Scale 2)1500KG - 1999KG -> 2.44 USD  /  Scale 3) 2000KG - 2499KG -> 2.38USD
    - Sales Order: Material ABCD / Qty order: 550KG = MISSING PR00 MANDATORY CONDITION
    - Reason: QTY 550 KG is out of scale
    The solution proposed, was to review the scales and if sales orders are being created in lower quantities, they need to set a low volumen for the initial scale.

  • Sales order: How to add pricing conditions at item level in BDC of VA01

    Hello Experts,
    Am writing BDC for sales order, in this process I need to add ITEM PRICING CONDITIONS, so, am selecting item and pressing the DOLLAR symbol button and am adding the conditions by pressing PLUS button in loop!! but am getting this erorr- Field KOMV-KMEIN (2) is not an input field!! when I execute it in we19-BACK GROUND only!! if I execute the same CODE IN we19-Fore ground, I dont have any issue!!  I checked this SDN (field status in config), Google, but did not helped me!
    Pls. let  me know is there any other way to add conditions at item level in VA01 in BDC code?
    THank you

    Hi,
    It is happening because the second row of the item level data screen is becoming display only. Please check whether In foreground mode you are pressing an extra enter to give data in the second row of the item level data after giving data in the first row and in BDC recording you have not recorded that 'Enter'.
    Regards,
    Gargi

  • No condition types at Item Level

    In the header of a sales order the Pricing procedure is triggered but at item level there are no condition types in the condition tab.
    I have maintained condition records for few condition types as well but still the condition tab is blank.
    What could be the possible cause of it?

    Hi Christino,
    Please check up whether these condition types for which you have maintained condition records are header condition or item conditions?
    Regards
    Mohammed Roshan

  • Condition tab is not appearing at item level in CRM 5.0 IDES

    Hi,
    I am trying to create Sample order in CRM ides but condition view at header level is blank and at item level condition view is not appearing.
    I have maintained condition record for condition types and it is visible in Material master. And correct pricing procedure is picked in sample order as I can see this in Header overview.
    I checked pricing procedure its correct. What else I need to check?
    Thanks for your reply.
    Nishith

    Hi Nishith,
    You can check if the item category is pricing relevant - field PRICING_RELEVANT in view CRMV_SALES_ITEM.
    Hope this helps,
    Kind regards,
    Vanessa

  • Urgent: Change custom conditions on item level

    Hi experts,
    could you please tell me how you resolve this issue, its very urgent? I´m facing the promblem that my condition type doesn´t get changed! I want only to change KBETR at item level. After CRM_ORDER_SAVE is called I can see, that order got saved, but nothing happens
    Please help me out! I think there is not a lot which has to be change. Here is my Coding:
    parameters: lv_head type crmt_object_guid default '...'.
    parameters: lv_item type crmt_object_guid default '...'.
    parameters: lv_kbetr type prct_cond_rate default '12'.
    insert lv_head into table lt_guid.
    insert lv_item into table lt_item.
    call function 'CRM_ORDER_READ'
       exporting
         it_header_guid                    = lt_guid
         it_item_guid                      = lt_item
       importing
         et_pridoc                         = lt_pridoc
         et_pricing_i                      = lt_pricing_i
    * CHANGING
    *   CV_LOG_HANDLE                     =
      exceptions
        document_not_found                = 1
        error_occurred                    = 2
        document_locked                   = 3
        no_change_authority               = 4
        no_display_authority              = 5
        no_change_allowed                 = 6
        others                            = 7.
    if sy-subrc <> 0 and lt_pridoc is not initial.
       write: / 'ERROR'.
       exit.
    endif.
    read table lt_pridoc index 1 into ls_pridoc.
    if sy-subrc <> 0.
       write: / 'ERROR'.
       exit.
    endif.
    read table ls_pridoc-pric_cond into ls_cond with key kschl = 'Z002'.
    if sy-subrc <> 0.
       write: / 'ERROR'.
       exit.
    endif.
    ls_input-ref_guid   = lv_item.
    ls_input-ref_kind   = 'B'.
    ls_input-objectname = 'PRIDOC'.
    ls_input_fn-fieldname = 'WAERS'.
    insert ls_input_fn into table ls_input-field_names.
    ls_input_fn-fieldname = 'KBETR'.
    insert ls_input_fn into table ls_input-field_names.
    *ls_input_fn-fieldname = 'ACTIVATE'.
    *insert ls_input_fn into table ls_input-field_names.
    insert ls_input into table lt_input.
    ls_pricom-ref_guid   = lv_head.
    ls_pricom-ref_kind   = 'B'.
    ls_pricom-pric_cond[] = ls_pridoc-pric_cond[].
    move-corresponding ls_cond to ls_cond_chg.
    ls_cond_chg-waers = 'EUR'.
    ls_cond_chg-kbetr = lv_kbetr.
    insert ls_cond_chg into table ls_pricom-cond_change.
    append ls_pricom to lt_pricom.
    call function 'CRM_ORDER_MAINTAIN'
       exporting
         it_pridoc         = lt_pricom
       changing
        ct_orderadm_h     = lt_header
         ct_input_fields   = lt_input
       exceptions
         error_occurred    = 1
         document_locked   = 2
         no_change_allowed = 3
         no_authority      = 4
         others            = 5.
    if sy-subrc <> 0.
       exit.
    endif.
    call function 'CRM_ORDER_SAVE'
       exporting
         it_objects_to_save   = lt_guid
       importing
         et_saved_objects     = lt_saved
    *   ET_EXCEPTION         =
    *   ET_OBJECTS_NOT_SAVED =
       exceptions
         document_not_saved   = 1
         others               = 2.
    if sy-subrc eq 0.
       commit work and wait.
    else.
       rollback work.
    endif.
    Best Regards
    Tanja

    Hi Tanja,
    I am probably not the right person for code but please review below listed former threads which should be helpful:
    http://forums.sdn.sap.com/thread.jspa?threadID=661004
    http://forums.sdn.sap.com/thread.jspa?threadID=596313
    http://forums.sdn.sap.com/thread.jspa?threadID=186588
    Best regards - Christophe

  • Freight condition calculated on header level , not at item level

    Hi,
    I am creating PO with 2 line items..
    mat X qty 1 price 100 INR
    mat Y qty 1 price 100 INR
    Now i have given freight as 500 INR in header level...
    My prob is freight is getting calculated based on number of  item level...
    It means if i have 2 item levels my freight is coming 1000 INR....
    it is adding based on line item.....
    but it shud come 500 INR....
    I want my freight to be added at header level......
    Utsav

    HI
    What will u do if in case freight shud be 500 + 500 = 1000
    So leave this condition as it is
    Goto Tcode M/06 ... and create a new condition for freight ... by copying the present condition type and then add it in pricing procedure
    But in "details "of this new condition type  put a tick mark against group condition and header condition.
    "To go into details of a condition type ... select the condition type and then click on lens button"

  • Crm_order_maintain ,changing pricing condition value at item level

    Hi,
    I am trying to change the pricing condition value at item level while creating sales order through CRM_ORDER_MAINTAIN.
    I am not able to change the condition value.
    Code is below.
          wa_inputfields-ref_guid   = wa_orderi-guid.
          wa_inputfields-ref_kind   = 'B'.
          wa_inputfields-objectname = 'PRIDOC'.
          wa_fieldname-fieldname    = 'KBETR'.
          append wa_fieldname to wa_inputfields-FIELD_NAMES.
          wa_fieldname-fieldname    = 'KMEIN'.
          append wa_fieldname to wa_inputfields-FIELD_NAMES.
          wa_fieldname-fieldname    = 'KPEIN'.
          append wa_fieldname to wa_inputfields-FIELD_NAMES.
          wa_fieldname-fieldname    = 'KSCHL'.
          append wa_fieldname to wa_inputfields-FIELD_NAMES.
          wa_fieldname-fieldname    = 'WAERS'.
          append wa_fieldname to wa_inputfields-FIELD_NAMES.
          INSERT wa_inputfields INTO TABLE it_inputfields.
    wa_pricing_add-KSCHL  = 'ZP06'.
    wa_pricing_add-WAERS  = 'USD'.
    wa_pricing_add-KBETR = '10'.
    wa_pricing_add-KPEIN = '1'.
    wa_pricing_add-KMEIN = 'ST'.
    INSERT wa_pricing_add INTO table it_pricing_add .
    wa_pricing-REF_GUID     = wa_orderi-guid.
    wa_pricing-REF_KIND      = 'B'.
    wa_pricing-PRICING_TYPE  = 'A'.
    wa_pricing-COND_ADD = it_pricing_add.
    wa_pricing-PRICING_PROCEDURE = 'ZVDSP'.
    append wa_pricing to it_pricing.
    Can you tell me how to overwrite the condition value while creating sales order using crm_order_maintain.?
    Regards,
    Indhra.E

    Hello Indhra,
    Check the CT_INPUT_FIELDS table, in the OBJECTNAME field you will find all the tables that are filled during the function call. Check those tables mentioned in the OBJECTNAME to look for any pricing related data.
    When your order is in change mode and you activate debug <b>just before you make the change</b>, the CRM_ORDER_MAINTAIN FM call contains <b>data only relevant for the change you just made</b>. In other words, you need to fill exactly the same tables as CRMD_ORDER does.
    E.g. You just change the pricing procedure and you see in debug that 5 tables are filled, you must do exactly the same in your code! It's quite anoying but you're using a low-level API FM that can handle ANY transaction type in CRM!
    Check it, it works!!
    <b>Reward points if useful!</b>
    Regards,
    Joost

  • Issue in using custom discount condition type in pricing agreement at Service Contract line item level

    Hello
    We are facing an issue while using a Z discount condition type in price agreement at service contract line item level.
    A Z Condition type has been created in ECC and assigned to the pricing procedure. This pricing procedure is downloaded in CRM and determined in the service contract.
    A condition maintenance group using this Z condition type is created in CRM and assigned to service contract item category.
    Condition records are created in CRM for this condition type/condition maintenance group for specific products along with sales org and discount percentage.
    But when the price agreement(using this condition type) is used at the item level of a service contract, the system throws errors (related to product/unit of measure and sales org, even though no issues seem to be there)and thus the price agreement is not allowed to be used.
    If anyone has worked on such kind of scenario, please get in touch, I will share more details for the same. 
    Regards
    Ankit Arora

    Dear Ankit,
    Once the pricing procedure is downloaded, please maintain the document pricing procedure at service contract header level, and maintain the customer pricing procedure at business partner sales area billing data.
    In spro, maintain the pricing procedure for the combination of sales area, document pricing procedure, customer pricing procedure.
    Please crosscheck whether the condition table is active or not.
    Regards,
    Maddy

  • Sales order condition change for Header and Item level..

    Hi Gurus,
    My requirement is as below..
    Business wants to create new sales order from reference.. While creating slaes order fron reference , need to populate header/Item level condition tab data from originally paid by the invoice for that refence sales order not from refence sales order condition price.
    I would like to how to bring this one, any user exit or copy control and any VOFm routine need to populate this kind of requirement.
    Any one have any idea please let me know.. It very urgent, give reward points for right solution..
    thanks,

    Hi,
    Here are the answers to your question
    > Is it possible to add/change condition types on the sales order (header and item level) for which invoice has been created already?
    I mean is it possible to add some surcharge condition to already invoiced order and than as result debit memo?
    The answer is No. You cannot add or change the condition once it is invoiced.
    > And one more question : Are there some time restrictions when debit/credit memo can be created? (I believe not, but I would like to have this confirmed, as I am not SD expert.)
    The answer is No again. There is no time restriction and you can create debit or credit memo immediately when the invoice is released to accounting.
    Hope this helps
    Thanks
    Mukund S

  • Header condition type should not be editable at item level

    Hi gurus,
    could  you please help me with the following question.
    Our requirement is to provide header discounts manually at header level which should not be editable at item level. So I've created condition type as Header condition.
    When we manually add this condition at header level in Sales order, it is copied to the item level and is not editable there.
    But after saving the SO, we find that the header discounts appearing at the item level becomes editable.
    Kindly  advice how to make the condition type as non-editable at item level.
    Thanks in advance.
    Sunny.

    hi Sunny,
    please check your condition type for discount in section 'Changes which can be made', wheather it used only for the header level or item level or both of it.
    if you want to make the condition is not editable in item level, then you must made the condition type just for the header level.
    beside changing the configuration in the condition type, you can protect it via BADI but it needs more programming.
    if you insist to use the BADI, you can made the implementation of class CRM_ORDER_FIELDCHECK BADI
    hopes it helps
    cheers

Maybe you are looking for

  • Can not use exported data

    When I transport tables from mssql2000 to oracle9i, using the export tool provided by mssql, I got a problem: Firstly, I can not select data from the exported table: the tables are exported successfully, but I can not select them in Oracle! It just r

  • Oracle 11g 2 installation blocked

    Hello, I'm installing the 11g release 2 Oracle version under a CentOS 6.3 virtual image, which is running on a CentOS 6.4 physical server. I've followed the steps about previous requirements showed in the "Quick installation guide", so I think that t

  • Why can´t I use original HPinkcartridges from one HP printer to another HPprinter it says use origin

    why can´t I use original HPinkcartridges from one HP printer to another HP printer, it says use original cartridges - but they are original?

  • JDBC in applet URGENT

    Hi, I have created an application by using JDBC,now i would like to convert this application into applet and put it online. So i register a domain name, create a jar file for this application and use browser to load it. But so far from what i know, o

  • TLS patch not working

    Hi all! I'm trying to apply a patch and it's not working. I've searched the web, metalink included and nothing... plus, the version numbers confuse me. Please advise. Thanks in advance! Here goes the apply verbose output (I'm sorry for the long outpu