x Want to participate? Join the group to interact
  • State Verified Answer
  • Replies 2 replies
  • Subscribers 136 subscribers
  • Views 3258 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
211
topics
418
replies
Sage Intelligence Reporting
121
topics
322
replies
S Orrock

X3 V7 - Purchase Request for Not Managed Items merging lines incorrectly on PO

SOLVED
Posted By

Hi

We have a client who uses Non stock (not managed) items on Purchase requests.

When a Purchase request is entered that may have multiple lines and meets the following criteria

- Same Product

- Same Supplier

-Same Dimension

X3 tries to be smart and merges the line when creating the PO and looks for a price list and as they are not managed and it does not have one, it breaks the price.  This completely breaks the system as we have workflow attached to the PR and no one can manually edit PO.

My understanding is that if I have set my products up as "Not Managed"  no price lists or anything should come into play.  can anyone explain why it does this, or are you thinking along the lines that I am that it is a bug.  We are on patch 6 and will be patching to patch 7 as soon as we can confirm some development.

Appreciate any feedback

Thanks

  • 0

    Further to this - more troubling is that we have identified that it is breaking the commitment table and not creating the PO line and turning it into a negative.

    I think we are now touching on a bug in the system.

  • 0 in reply to S Orrock
    verified answer

    Please note we received this

    Since fix 13727 (entry point request 87834) in list 24, in V6, the entry point ECLBESOINS from process TRTACHCDE1 has been amended and a new criteria has been added: ECLAT_PRI.

    This triggers 2 SEPARATE  lines in a purchase order, if a purchase request contains 2 lines with the SAME product with the SAME supplier AT A DIFFERENT PRICE.

    Break-up per line price (1=no, 2=yes). This is possible when we come from grouping planning (FUNMPICKA) or button “order” from the purchase request function (GESPSH).

    It allows not grouping 2 lines of a purchase request if their prices are different.

    In this context of grouped lines having the same prices: the net price zones, the gross price, the currency, rate type, taxes, charge and discount are kept, and contain values from the first document line.

    Be careful, the field is manageable only if variable TRAIT is set to 3.

    It is advisable to test this context (If TRAIT = 3).

*Community Hub is the new name for Sage City