This transformer “SEPA - Send Sepa Credit Transfer to file with CORE 03 transformer” is what our German Bank accepted as replacement for the phased out SEPA XML format in November of 2023. I had posed a question, in a closed-for-comment posting, and had not gotten this detail response. So we determined what to use by trial and error. IFS Support in US got us part of the way (IFS Consulting never responded). I suppose this information applies to later versions of IFS. SEPA - Send Sepa Credit Transfer (DE) APPLICATION_MESSAGE OUT1 SEPA - Send Sepa Credit Transfer (CORE 03) Search Op Match MESSAGE_FUNCTION equals SEND_SEPA_CREDIT_TRANSFER RECEIVER startswith CORE_001.001.03 SEND_SEPA_CREDIT_TRANSFER_CORE_03_transformed_84366809-80b6-40f6-aac6-38f7aa8a7b06.xml<
text from bank regarding SEPA transitionI am looking for guidance on which one of the many XML Transformers in Connect should be used in Germany to meet the October 2023 mandate for the SEPA format.We currently have a rule with MESSAGE_FUNCTION = ‘SEND_SEPA_CREDIT_TRANSFER_DE_04’ that outpus the SEPA XML file to the Application Server. Our accountant in Germany has raised a red flag advising that we must use a new format. However, I am in US and unfamiliar with the work flow and handling of the SEPA XML file. No guidance that I can understand has been provided to me.
We have been archiving some Application Messages to the Application Message Archive, using an example of Database Task Chains (‘Manage Application Messages’) that exists. That all works. At one point I thought there was an example of a Chain Step to purge data from the Application Message Archive, but all I find now are statistics and message cleanup tasks.I do not find table FNDCN_MSG_ARCHIVE_TAB referenced in ARCHIVE.API. Is there a task or am I forced to go the Data Management / Data Archive approach?
Has anyone ever experienced this customer order failure in background jobs:The Customer Order redeploys a Serial tracked Part from Inventory to a Customer. The Serial Part itself was produced in IFS 2004/Apps7.5 and gets returned, serviced, and put back in stock multiple times over its life. PROCEDURE............: Customer_Order_Flow_API.Process_From_Report_Picking__ARGUMENTS............: START_EVENT¬85^ORDER_NO¬22509337^PICK_LIST_NO¬2527471^LOCATION_NO¬^ERROR_TEXT...........: ORA-01086: savepoint 'EVENT_PROCESSED' never established in this session or is invalidORA-06512: at "IFSAPP.CUSTOMER_ORDER_FLOW_API", line 2905ORA-20111: Site.NOTEXIST: The Site "*" does not exist.ORA-06512: at "IFSAPP.CUSTOMER_ORDER_FLOW_API", line 2905ORA-06512: at "IFSAPP.CUSTOMER_ORDER_FLOW_API", line 2924ORA-06512: at "IFSAPP.CUSTOMER_ORDER_FLOW_API", line 2337ORA-06512: at "IFSAPP.CUSTOMER_ORDER_FLOW_API", line 2342ORA-06512: at line 1ORA-06512: at "IFSAPP.TRANSACTION_SYS", line 1452ORA-06512: at "IFSAPP
As of right now we have 75 fixed assets on our Co. 99 ledger that we are looking to transfer to Co. 35 without affecting the base value and current depreciation on the 75 fixed assets.Is there such a function or process in IFS Apps9 that can accomplish this?
I’m wondering how complicated automating a cost reclassification in the general ledger (manual journal entry?). We have an new condition where a PO issued by Company “B” for service work performed to upgrade equipment. A piece of the servicing is provided by a third party, paid for on that Company “B” issued PO. For certain vintage units there is an additional charge amount and that amount needs to be charged to a Company “A” account.What does it take to configure an automatic way to transfer a purchase order/supplier invoice cost from one Company/Department to another Company/Department?
Seeking confirmation that Route Planning works for Day of Week and not Day of MonthAdmitting that I’ve never used Delivery Route functionality and now have a need to set up day of the month shipping day for Customer Orders. I can see that a route to set the delivery date to a particular day of the week is supported but wondered if there were some configuration tricks to allow eliminating weeks of the month from the shipment scheduling.We don’t have a Customer Schedule to release against, orders just appear during the month (usually on the same day of the week) and we want to try consolidating deliveries to once a month (basically ignoring the customer’s request date and moving them to once a month on the same day (e.g. third Thursday).
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.