We currently utilize Incoming Customer Order to process incoming EDI xml files. Today, we let IFS calculate the price of the product based on price lists and customer agreements, and overwrite any price received in the file. In the future we would like accept the price from the incoming file instead. We have not been able to figure out how to change this, though. Are we missing some flags on the customer or in the xml file? Do we need a different solution to bypass the pricing set up for manually created orders? Current xml price tags used:<UNIT_PRICE_IN_OUR_CURRENCY>65.01</UNIT_PRICE_IN_OUR_CURRENCY><UNIT_PRICE_IN_SUPPLIER_CURRENCY>65.01</UNIT_PRICE_IN_SUPPLIER_CURRENCY> We did notice that the “Original sales Price” in Incoming Customer Order does not populate: Price in the Customer Order: Thanks for any suggestions on this.
We are using Apps 10 upd 13 and looking for some suggestions on how to trigger two different emails with different report layouts attached when our Invoices are printed. We have been testing with the setup below. An event action (PDF_REPORT_CREATED) that has been in use in our prod environment for a couple years. This sends an email with our default layout invoice to the correct recipient. A new Report rule that triggers a different email and recipient. This email successfully sends to the correct recipients at invoice Print We are able to define the layout in this report rule, but it also changes the layout for the event action email, which is not what we are looking for. We tried to use multiple report rules or to combine the two emails into one report rule but that did not work. We do not want to use the PDF_REPORT_CREATED for our new email because we need several fields to be pulled into the email that are not available through the pdf_parameters. Are there other options tha
We are currently on apps 9.7 and need to set up a second export license for a scenario where a purchased material must have a license, and can be controlled by multiple licenses, but in a way that we need to select one or the other when purchasing it. Both licenses should not be connected to a single Purchase Order line because the licenses have separate quantities allowed to be licensed.Example:Part No: 923License: 8 Qty licensed for PN 923: 3500 This license is already in use and should be connected when the material is purchased for the purpose of being used in productionLicense: 9 Qty licensed for PN 923: 250 This license is new and should be connected when the material is purchased for the purpose of being used internallyPurchase Order: Line 1/Rel 1 - PN 923 - qty 250 - should be connected to license 9 Line 1/Rel 2 - PN 923 - qty 500 - should be connected to license 8On the PO for this material each line shows as "partly connected" when only connected to
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.