Build Highlights

Now different codes can be used for the same MDC unit. This is made possible via a new MDC mapping program which is accessed via the MDC mapping option in Work with units in the Demanding company.

This program allows an item’s MDC unit in a Demanding company (e.g., KPL (which means pieces in Finnish)) to be mapped to the unit code used in the Supplying company (e.g., STYCK (which means pieces in Swedish)). The unit used on the sales order line in the Demanding company will be ‘translated’ using this table before the order is sent to the Supplying company.

Now, a new Pricing date field has been introduced giving you an additional alternative by manually entering a pricing date.

Pricing date has been implemented in the following:

• Purchase order header panel
• Purchase order enquiry
• Supplier comparison enquiry

Any manually entered date in the Pricing date field will be used to retrieve a purchase price regardless of the setting in the Price order date field. To retrieve new prices after changing the Pricing date on the purchase order header, use the Re-price option on all lines.

Note: Purchase price is retrieved in many places in the system where no purchase order is present. No changes have been implemented to those processes.

Prior to this enhancement, it could be time consuming to update the retail price for items that had the same retail price.

Now, if no retail price is defined on the pricing source from where the sales price is retrieved, the retail price from the item base price (i.e., the Standard price list on the DIS control file, Pricing policies, Sales panel) will be used. This expedites updates when the retail price is always the same for the same item.

See Changes to Intrastat returns as of 2022 under Financials in Build 22.0.4 for more information.

Changes have now been implemented whereby multiple restrictions can be re-scheduled backward in time but only until current date + days before shortage for BtB orders.

Now the search for component is according to exact match in all functions.

The following programs have been changed:

• Basic data structure maintenance (BAS003B)
• Basic data structure enquiry, one level (BAS202B)
• Basic data master BOM maintenance (BAS071A)
• Basic data master BOM enquiry (BAS271A)
• Product costing on-line (BAS050D)
• Product costing enquiry (BAS204D)
• Manufacturing order maintenance (BAS002C)
• Manufacturing order enquiry (PRO201O)
• Project order maintenance (POM060G)
• Project order enquiry (POM260G)

In addition, a new AUDR035 (Update Invoice Header with ASN number) program has been added to process the new field. This AUDR035 program will be called from an existing AUDR100 (EANway – ASN Driver program) program.

A new Barcode field has been added to enter the barcode that needs to be scanned in the ‘Work with receptions – Details – in stock unit’ panel.

The system will use the barcode to retrieve GTIN number, NDC item code, Batch Id and Use by date.

Prerequisites:

• New ‘BCSCNLRE’ Function control must be active.
• Item must be set up as batch control.
• GTIN number or NDC item code setup must exist for the item.
• GS1 separator should be set up in Pharma control file. If the setup is not done then, by default, the system will use ‘#’ as GS1 separator.

The availability check performed in the Supplying company after entering an MDC order line in the demanding company did not follow the standard rules for sourcing which meant that Auto fulfilment was not considered, i.e., no date/quantity adjustment nor split of line nor auto creation of BtB could occur.

This has now changed so that the same sourcing will be performed for MDC in the Supplying company, as for a normal order line created in a single company.

As a result, the following has been implemented:

MDC availability enquiry
An Order fulfilm rule field has been added giving the user the possibility to use different order fulfilment rules and thereby simulate different sourcing results. Informational messages will be displayed on the bottom of the panel regarding date/quantity adjust, BtB deliveries. Regarding split of lines, an extra informational message line will be visible showing the delivery from another warehouse or with another dispatch date.

Sourcing policy simulation
If the sourcing simulation results in an MDC/BtB delivery, a new panel can be viewed with information about how the sourcing in the supplying company was performed. In addition, since sourcing can result in date/quantity adjusted and split of the delivery in the supplying company, both the Primary warehouse from where the delivery will take place, as well as the Secondary warehouse (in case of split of lines) from where the second delivery will take place, as well as the Available quantity and Available date info for both the Primary and Secondary warehouses will be visible.

Sales order enquiry, Order lines, Additional info 6 panel in the Demanding company
The following new information will be shown for detailed order line information related to MDC:

• MDC ord type: Displays the order type used for corresponding sales order in Supplying company
• Trans/Direct: Denotes if this order type is type BtB transit or direct.

If known, the real VAT number is reported, and the country specific VAT number validation check is performed.

If not known, the system now provides the following three formats for ‘dummy’ VAT registration numbers:

• For Triangulations: Receiving country code and 12 number 9’s
• For non-triangular transactions:
  • For a Business entity: QV999999999999
  • For a private individual: QN999999999999

Two new variables, i.e., Country of origin and Partner ID (VAT identification number) became mandatory in the reporting of export data. As a result, the Country of origin and VAT registration have been added to applicable files and are now included on the Intrastat FI Declaration printout.

The existing V7M_VAT report has been enhanced with a second version, i.e. JPK_V7M(2) to adhere to this requirement.

The same menu item is used, and the creation program creates V7M_VAT in the first xml version (valid between 1.10.2020-31.12.2021), or with the additional information depending on the selected reporting period (selected on the selection panel).

Two new variables, i.e., Country of origin and Partner ID (VAT identification number) became mandatory in the reporting of export data. As a result, the Country of origin and VAT registration have been added to applicable files and are now included on the EU Intrastat Declaration – Dispatches printout.

When automatically creating a Batch ID via a Batch mask, the variable(s) or combination of fixed constants (texts) and variable(s) selected for the Batch mask denotes how the Batch ID should be generated when receiving purchased items into stock.

This new RCS variable will retrieve the reception sub-line number to the batch. This is advantageous in situations when large quantities are received, creating multiple pallets where every pallet needs to have a specific batch ID. It avoids duplicate batches.

New transaction types have been created to account for gains and losses in any exchange rate differences less than zero.

(Existing) The following transaction types can be used to account for gains and losses in any exchange rate differences greater than or equal to zero when matching A/P invoices:

811 (Exchange rate diff Invoices; used if there are any differences between the exchange rate on the supplier invoice and the purchase order)

763 (Exchange rate diff invoices proj; used for project orders)

(New) The following transaction types can now be used to account for gains and losses in any exchange rate differences less than zero when matching A/P invoices:

839 (If the Exchange rate difference to be posted for INVOICE is less than Zero then this new transaction type will be used to create the transaction).

783 (If the Exchange rate difference to be posted for INVOICE Project is less than Zero then this new transaction type will be used to create the transaction.)

The Primary quantity is updated with the order quantity when the order receives its first status, and the order line is not a backorder line. Then the primary quantity is locked. If the order quantity is changed, the primary quantity remains the same.

It is now possible to add a supply exception policy to an item/warehouse with planning method 6 (Purchase suggestion, Supply plan).

• 31 VAT code list instead of the previous 19 VAT code list
• The new VAT-return re-uses the Standard Tax Codes from the SAF-T standard. (Note: the new VAT-return must not be confused with the SAF-T Financial file. Only the codes will be re-used. The VAT-return will still be at a very aggregated level).
• From electronic forms to digital interaction
• No longer numbered fields, these are replaced by a dynamic list of specifications

• For the purchase order line reception menu option, it is now possible to create EAN code if it does not exist in the Item file.
• Backlog code is displayed on panels and can be changed at reporting.
• For item line reception, the item label printout selection panel will be displayed after confirmation if the ‘RFRECLBL’ function control is activate and the supplier is defined in the Item label print control table.
• Putaway: new menu option with start panel displaying receiving location. From this panel you can select to do putaway.

In specific cases, a legal obligation could arise, necessitating the use of a different exchange rate for calculating the VAT amount in the local currency. In these instances, the exchange rate defined in SROLBV (an interface file between DIS and FIN or Medius and FIN module) is employed instead of the one initially entered at the time of the invoice. For period for VAT calculation is calculated either from the Invoice date or the Reception date, if period is not available in SROLB file.

Now the exchange rate difference on the VAT amount is posted on a new Pseudo, which is XVATDIF.

The following has been implemented:

If the Australian (AU) application is not active, then the user will not be allowed to select the above-mentioned fields. An error message will be issued if the fields are selected for a “non-Cash Book” document type

As per new ruling on the compliance of the Polish VAT regulations on the relief for bad debts with EU regulations, it is mandatory to correct declared input VAT amount if an invoice is a bad debt invoice. After the invoice is paid, the related input VAT amount can be reversed.

The following has been implemented for accounts payable:

• Invoice not paid and overdue greater than 90 days and other criteria will be selected for Bad debt proposal.
• VAT correction amount will be calculated.
• Generate the G/L posting for VAT for the unpaid and partially paid invoices.
• Paid bad debts proposal: If the invoice is paid, then reversal of G/L and VAT posting will be created.
• Log file will be generated for the selected invoice.

A Keep open locations field has been added on the Item/warehouse update panel which eliminates the need to count all locations before update.

When set to Y, the counted location(s) (location done, status = 60) will be processed. Non-counted location(s) will remain open for counting. Mobile stock take list will receive status 40. If all locations are counted, then the mobile stock take list will receive status 60.

When set to N, the counted location(s) (location done, status =60) will be processed. Non counted location(s) will be released, and no stock changes will occur. The mobile stock take list will receive status 60.

A Difference report can now also be generated via the new Print control list option on the Work with mobile stock takes panel. This report provides detailed information of the counted location. For example: counted quantity; quantity present in location; difference between counted quantity and the quantity present in the location, and the cost difference.

Method: salesOrderHeaderHoldReason.add

Parameters: order
reasonCode
releaseHandler
ReleaseGraceDays

Note: The default and replacement functionality can be used to set the “releaseHandler” default value using group/level/key as:
Group…………… SALESDFT Sales defaults
Level…………… HOLDORDH Hold sales order header
Key…………….. RELEASEHND Release handler

To adhere to this legal requirement, a new Office code field has been added to the Italian invoice control file. This field is used by the Java program that creates the xml to add the value into the xml tag denoted above.

As a result, the DC1/UPS integration programs have been changed to use the token-based authentication known as OAuth 2.0.

There is new API call required to generate token and then use the desired API along with the token.

The following changes were implemented:

• Allow specifying in BP file, if a BP is ‘Private individual’ This controls QV999999999999 vs QN999999999999
• Extended Intrastat file SROECF with field ‘VAT number of trading partner’
• Updated the following programs which populate SROECF so that the field is populated:
  • DIS invoicing – use dispatch address info
  • A/R manual invoice entry/Intrastat info
  • Sundry invoice entry/Intrastat info
  • Journals in error maintenance
• VAT number in triangulation – special rules to establish VAT number in DIS invoicing
• Changed Intrastat programs to get VAT number from SEOECF

These new APIs make it possible to download details of multiple or individual pricing methods. Offset and limit control parameters with a ‘total count’ response parameter are also included.

The following API’s have been changed:

• itemSalesPriceListHeader.update
• itemSalesPriceListDetail.update
• salesPricingMethodDetail.update
• salesPricingMethodDetailLimitDiscount.update

To be able to display the UNSPSC for a product on the e-commerce side, the following has been implemented:

• a new Work with UNSPC codeset program has been created to store details like code and description.
• A new UNSPC code field has been added on the Basic data panel of Work with items. This is an optional field, but if entered it must be a valid UNSPSC.

This new option, which allows you to rename existing user profiles, is only available to users with system administration authority. All updates for each user profile will be printed in a spool file.

For mass updates, the user with system administration authority may use mapping file SROUSPRNM (which must be updated manually, or imported first) and then call or submit program ASGR964.

• Work with standard audit files (SAF-T)
• Norwegian VAT report 2022

The IFS communicators to be used for respective processes are now defined in Norwegian SAFT control file.

This functionality, which is aided by a new Fast mov function key on the initial Work with inventory panel and a new Fast movement panel, is not applicable for the following scenarios:

• Transit and NCC related movements
• WMS controlled warehouses
• Date handled batch items
• Serial number-controlled items
• Serialized tracking items
• Pharma serial items

Existing authority controls related to warehouse movements are also applicable to Fast stock movements.

A new interface / API per file used in defining the item purchase prices using purchase price list has been added.

API s have been created for the following purchase price related files:

• SROPPU: Item purchase unit price
• SROPPP: Item purchase unit price per period
• SROPPRQ: Item purchase price information, qty dep prices

The following new API methods have been added:

itemPurchasePriceListHeader.get
itemPurchasePriceListHeader.add
itemPurchasePriceListHeader.update
itemPurchasePriceListHeader.delete
itemPurchasePriceListHeaderLimitDiscount.get
itemPurchasePriceListHeaderLimitDiscount.add
itemPurchasePriceListHeaderLimitDiscount.update
itemPurchasePriceListHeaderLimitDiscount.delete
itemPurchasePriceListDetail.get
itemPurchasePriceListDetail.add
itemPurchasePriceListDetail.update
itemPurchasePriceListDetail.delete
itemPurchasePriceListDetailLimitDiscount.get
itemPurchasePriceListDetailLimitDiscount.add
itemPurchasePriceListDetailLimitDiscount.update
itemPurchasePriceListDetailLimitDiscount.delete

A new M-order batch clearance contr (BCHSHORT) function control has been introduced which, when active, will allow the release of the manufacturing order even if there is a material shortage for the component(s) (i.e., shortage code 1).

When this function control is active the user will be able to release the order on the Manufacturing order batch clearance, Overview panel via the Release option (not via the Release all function key). The system will display a warning: “Warning: Shortage exists for order. Confirm to release order”. To confirm the release, press enter.

The following programs have been changed to load all lines at once for the order/item, thereby eliminating the need to scroll down before clicking on a column to sort the information:

• BAS003B, Bill of material maintenance
• BAS003C, Bill of routing maintenance
• BAS202C, Structure enquiry
• BAS202B, Structure enquiry
• BAS202E, Bill of routing enquiry
• PRO002C, Manufacturing order maintenance, material
• PRO002G, Manufacturing order maintenance, operation
• PRO201O, Manufacturing order enquiry, material
• PRO201I, Manufacturing order enquiry, operation

This is controlled by a new Material/Capacity control (MTRLCAPC) function control.

When this function control is active all materials and operations for an item or manufacturing order will be displayed (the selection field for shortage code will be defaulted to blank).

When this function control is inactive the materials and operations will be defaulted to display only shortage.

• Work with tessera sanitaria proposal
  (IFS communicator defined in Tessera sanitaria control file)
• Maintain proposal (COMUNICAZIONE POLIVALENTE)
  IFS communicator defined in COMUNICAZIONE POLIVALENTE Control file)
• Electronic VAT declaration period
  (IFS communicator defined in Italian fiscal control file)
• Communicate invoice issued and received
  (IFS communicator defined in Italian fiscal control file)

• Create JPK_V7M
  (The IFS communicator to be used is defined in JPK_V7M control file)

The following programs have been changed to load all lines at once for the Master BOM/BOR, thereby eliminating the need to scroll down before clicking on a column to sort the information:

• BAS061A, Bill of routing maintenance
• BAS071A, Bill of material maintenance
• BAS261A, Bill of routing enquiry
• BAS271A, Bill of material enquiry

The hard-coded IFS folder name has been removed from the following programs, thereby allowing the use of the IFS communicator interface to set up customer-specific folders on the IFS for A/P payments:

• NOFC832A
• NOFC833A
• NOFC933A

In addition, the following file names have been changed to adhere to system standards:

• NOOTBS has been changed to NOTTBS
• NOOOCRX has been changed to NOTOCRX

To facilitate the re-use of the pallet number from the supplier’s pallet label for internal purposes instead of having to generate a new number, a new Enter/scan pallet number option has been added on the Work with receptions, Details panels in the XT UI client which is applicable for Warehouse Management activated items. After clicking this option, the user will access a new Enter/scan pallet number panel where you can manually enter or scan the supplier’s pallet number.

In addition, the Pallet number and Pallet type fields are now always visible and input-capable on the Purchase order line reception, Update panel in the Mobile Warehouse client to facilitate the manual entry/scan of the supplier’s pallet number for internal purposes.

The validation and update are handled in the API program(s). As a result, the following forms have been changed to handle the validation and update:

1. Purchase order line reception – nurfLineOrderReceptionUpdate
2. Picklist, pick – nurfPartPickListsPick
3. Picklist, picking and packaging – nurfPartPickPackListsPick
4. Pick for location put away – nurfLocationPutAwayLines
5. Put for put away from location – nurfPutForPutAwayLocation
6. Pick for location put away – nurfRecLocationPutAwayLines

To facilitate the possibility for the user to pick all demand to a specific zone, a new Zone replenishment menu option has been added in the Mobile Warehouse client, allowing you to select by zone.

The first panel displays all the zones for the user’s warehouse which holds suggestions, as well as the number of instructions that exist by zone (to zone). After selecting the zone, all suggestions for the zone will be displayed with the possibility to pick/put single lines or put all.

The following new forms have been added:

1. Zone Replenishment – nurfSelectZoneReplenishment
2. Pick for zone replenishment – nurfToZoneReplenishmentLines
3. Put for zone replenishment to zone- nurfZoneReplenishmentPickedLines
4. Put for replenishment to location – nurfPutForZoneReplenishment

The following new manager programs have been added:

1. MGRR1034A – replenishmentSuggestionsByZoneRF.ge
2. MGRR1034B – replenishmentInstructionsByZoneRF.get
3. MGRR1034C – replenishmentSuggestionRF.get

Reported qty (the reported quantity value is, e.g., beneficial information if the issue you are creating is a return to warehouse)

Order link (this information is displayed when you toggle to Connect mode by clicking the Normal/Connected function key to view the connected element item lines. It is, e.g., beneficial to see the elements lines that are connected to a purchase order if the issue you are creating is a return to warehouse.)

Acquisition type

• The process now requires IFS communicator type named INTRASTAT to be defined under Work with IFS communicator types.
• Fix program FIXR056801 can be used for creating the IFS communicator type with default file name format and root(/) as output directory.
• This default setup can be changed in Ww IFS communicator types.
• IFS communicator type variable /P is mapped to use ‘Country’ from the selection panel.

Now, a warning will be displayed if no selections are made on that panel denoting that all purchase orders will be printed.

As a result, the possibility now exists to add 15 rows, each of which can have a maximum of 35 characters for unstructured references. This results in a total of 525 characters allowed, enabling users to use this capacity for unstructured references in future accounts payable payments.

• Supplier maint pgm DKFC618
• Supplier enquiry pgm DKFC619
• Supplier print pgm DKFC621
• Supplier delete pgm DKFC622

An IFS communicator named INTRASTAT now exists. The user can specify the IFS folder name in INTRASTAT.

When the EU Intrastat declaration program runs, an excel report is generated (for both Arrival and Dispatch declaration data) and placed in the IFS folder defined in INTRASTAT in the IFS communicator.

(OpenApi v.1.10.0 requires these MGRR programs.)

Outbound

Business partners – Updated

Items – Updated

Item Balance per warehouse – Updated

Stock inbound transactions – New

Stock outbound transactions – New

Sales orders – Updated

Purchase orders – New

Inbound

Purchase order – Updated

• The following UI columns, that can be activated via the Edit columns feature, have been added: VAT handling code, Document date, Voucher date, Amount trans curr, Trans curr, Ref amount syst curr
• Header field Total system amount has been added on FSR11101 panel.
• Unbalanced doc function key has been added in all modes i.e., Valid transactions/Invalid transactions/All transactions. The new panel accessed via this new function key will display a list of unbalanced documents.

• Phase description
• Cost code description

Print Accounting history list is changed to use IFS communicator.

• The process now requires IFS communicator type named FLFACCHIST to be defined under Work with IFS communicator types.
• Fix program FIXR122701 can be used for creating the IFS communicator type with default file name format and root as output directory.
• This default setup can be changed in Work with IFS communicator types.

• The EAN numbers option on the Item unit panel has been changed to GTIN numbers
• On all the subsequent panels the EAN text has been changed to GTIN
• Description of the EANCRT, EANSRCH function controls has been changed and the EAN word has been replaced with GTIN. Function control name remains the same
• Previously, the validation of the EAN number (check digit) was controlled by the EANCHECK
  function control. This check has been moved from function control to base setup and extended to check all GTIN formats. The EANCHECK function control has been removed from the system and in all places where this function was used, changes have been implemented as if the function control is active.
• All system level messages have been updated and EAN has been replaced with GTIN
• All output documents where EAN were printed have been changed to GTIN
• Printer and display file translation fields have been changed from EAN to GTIN
• Existing APIs have been updated to introduce new ‘gtin number’ parameter along with existing ‘ean number’ parameters.

An Item search/positioning field has been added to this panel to facilitate the search.

• manufacturingOrderHeaders.get
• manufacturingOrderMaterials.get

API methods included in API release 1.12.0

The following modification has been implemented to improve performance:

The system now retrieves and stores a maximum of 9999 records in the work file and, as previously, displays that maximum.

To ensure that the Voucher date corresponds with the Balance period & Elimination period, the following modification has been implemented:

The Month end date defined in the GL control file will be used to post the transaction in Balance period & the first month day will be used to post transactions in Elimination period.

Two new fields have been added in Work with SIE export options. They include:

Chart of account typ and #TRANS date control.

These fields work as follows:

If the Chart of account typ field is filled (not blank) then for Transaction type 01,02,03 and 04, Record #KPTYP will be created in SIE file.

If the #TRANS date control field is set to “Y” for Transaction type 04, then the TransDate is calculated from the period of the transaction instead of the document date. The calculation of the #TRANS/transdate is as follows: If it belongs to the transaction period, keep it unchanged. If it is earlier than the transaction period, change it to the first of the period. If it is later than the transaction period, change it to the last date of the period.

If the #TRANS date control field is set to “N”: No changes to current handling, i.e., the TransDate is calculated from the document date.

This functionality is now available in Mobile Warehouse. Note that Inventory adjustments are not allowed to be performed in combination with CMI processes since Inventory adjustments require a logical warehouse.

The following has been implemented:

A new record format to print Language code along with other information associated with the language code such as Date separator, Date form at, ISO language code, Decimal format and thousands separator have been added to the printer file for the following sales related documents:

DMR312, DMR322, DMR337, DMR344, DMR190, DMR432 (included in DMR312), DIR358, SIPR121, DSR321, WMR961, DSR186, DMR333, SOR307, DSR321, and DMR332.

The name of the record format is PR3LG01 and this new record format has been added only to the J or P3 type 3 printer files to include the above-mentioned information in the XML output of the aforementioned documents. This information can then be used within interform designer to modify the templates as desired by the customer.

When interactive inventory adjustments and inventory movements are performed in the system, and the value of the adjustment or movement is above a given limit, approval is needed from a person with a higher authority limit.

Note: NCC movements and any batch process is not in the scope of current modification.

The following has been implemented:

– New “Approval tasks” Menu.

– Three new menu options for set-up and approval:

1. Work with approval routines – the system comes preloaded with the *INVADJ (Inventory adjustments) and *INVMOV (Inventory movements) routines set to Inactive (I) by default. If you want to active these routines for authority limit handling, set the Status to Active (A).
2. Work with approval routine matrix
   In this routine you:
   • Register the applicable users or roles that have the authority to approve / reject the above-mentioned inventory transactions.
   • Define the value / range of lower and upper limit for which the applicable users or roles have authority. You can also register a ‘super user’ whereby no value or range of lower and upper limit is entered. This user would then have authority to approve all inventory adjustments and inventory movements.
   • Delegate authority to another user to handle the approval / rejection process for an authorized user when that authorized user is not available (e.g., temporary absence like vacation, leave, etc).
3. Work with approval routine transactions
   In this routine the user with authority can either approve or reject the transaction. One can also view the transactions; enter remarks to explain why the transaction was rejected; and reset a transaction that is in a rejected status.

– New APPINVTRAN Event ID in Alert Management.
It is recommended that Alert Management be activated to be able to configure the system to notify (via email) the receiver(s) (i.e., user(s) with approval/rejection authority) that an inventory adjustment and/or inventory movement needs to be approved. If Alert Management is not activated and configured, the users with approval/rejection authority will have to periodically check the Work with approval routine transactions for any pending approvals/rejections.

IFS communicator – the Communicator ID can be defined by an authorized user and set up in dedicated control file, or it can be hardcoded.

Create report files – when you set this field to YES, the EU VAT sales report is generated in .CSV file format, which includes a header, and stored on the IFS for file transfer/processing by the tax authority, or bank, or other entity.

A validation has been added to prohibit the inactivation of an item in the Item file if it exists on an open Request and Return.

The following has been implemented:

1. A new Work with E-invoicing formats table to store the E-invoicing formats.
2. A new E-invoice function key on the Business partner maintenance, DI documents panel. When pressed, a new Business partner maintenance, E-invoicing formats panel is accessed to display and activate E-invoicing formats. See 3) below.
3. A new Business Partner file maintenance, E-invoicing formats panel. The user can activate the E-invoicing for a selected E-invoicing format on this panel. Only one E-invoicing format can be activated at one time.
4. The Invoicing program DMR344 has been modified to include the following in the Invoice document xml:
• E-invoicing format for the business partner.XML tag
• GLN number (Defined on the Party identifier field at the Business partner address level). XML tag
• Line level VAT percentages. XML tag
• VAT percentages defined for header fees such as Freight, Postage, admin etc., XML tags <VATP_T03>,<VATP_T04>,<VATP_T05>,<VATP_T06>,<VATP_T7>.

• Added default and replacements
• Changed A/P invoices posting to send information to integration layer about A/P invoice posting.
• Created posting for VAT amount using VAT interface file (SROLBV) during final invoice posting

1. Created new pseudo accounts XRA= GL Balance revaluation gains and XRB=GL Balance revaluation losses, specifically designated for G/L revaluation postings.
2. The new pseudo accounts replaces the existing XRL (replace by XRB) and XRG (replaced by XRB) pseudo accounts.
3. It will be possible to add currency code as variable (suffix) to fixed XRA and XRB part.

The Quantity on hand is now being updated from the Warehouse balance file. Corresponding JETFORM changes have also been implemented.

A new CRTQUOPROS default and replacement group has been created which can be used to define default templates for “Customer” and “A/R” panels.

Group = CRTQUOPROS (Quotation default for BP type 9)

Level = DEFAULT (Store Business Partner default)

Keys = A/R (A/R level default), and CUSTOMER (Customer level default).

In the Character value field, the field name of the ‘default’ can be defined. If keys are set up, then certain values will be referred from BP defaults. If keys are not set up, then it will still be possible to create sales quotations for prospective customers, but some mandatory entries will need to be completed by the end user.

Note: The purpose of using Customer and A/R defaults in default and replacements is to avoid manual entries of important values used for sales quotation creation. Not all values from defaults are utilized. If there is a need to use all values, then it is better to create a dummy customer instead of a prospective customer.

• Item is a serial number item with the Serial no tracking field on the Item file maintenance, Inventory information panel set to 2 (= Always mandatory)
• Any warehouse is activated for the item with WHM also set as active at Warehouse level.

When Transfer prices is set to N then no sales price is retrieved in the Supplying company and no sales price is returned to the Demanding company. Previously, no warning was displayed in the Demanding company to denote that there was no sales price for the item in the Supplying company. This lack of warning could make it challenging to determine why the corresponding sales order would end in error in the Supplying company.

The following has been implemented for the MDC process when Transfer prices is set to N in the setup:

A warning will be issued in the Demanding company if there is no sales price set up in the Supplying company.

• Fix Program FIXR167201 added.
• Preload INGR950 is updated with new API’s.
• Updated the following API methods:
  salesOrderHeader
  salesOrderHeaderAddress
  salesOrderHeaderText
  salesOrderLine
  salesOrderLineText
  salesOrderLineAddress
  companyInfo.get
• New API method added:
  textTypeDocuments.get

Previously, when the service agreement was converted to a service order, all text lines from the service agreement were transferred to the service order. The result of which was that the service order related notes and service agreement related text lines ended up in the same Text set on a Sales order. If the Text set was common, the notes were printed on every document, instead of being independent. It was not possible to have different print Documents for each one.

Changes have been implemented and will work as follows:

1) Create a new service sales order and add text only at notes id level. In the service SO the text set must be created for notes id and the connected document also must be activated as per notes id setup.

2) Create a new service sales order for which text is added only at service agreement level. In the service SO the text set must be created based on service agreement text and the connected document must also be activated based on the master setup *SVCORDHDR. Note: As per the current system design, on service agreement level it is possible to have different documents to print and those are valid at service agreement level only. All those documents are converted into a single set of documents at service order header level. Hence, when the service SO is created, the system activates the documents based on *SVCORDHDR level not on *SVCAGR level.

3) Create a new service sales order for which text is added at both notes id, and service agreement level. The system will create the new text set for service agreement text after the notes text set.

4) Create a new service sales order for which text is added at both notes id, and service agreement level. The system will create the new text set for the service agreement text after the notes text set. If there is another agreement with a text set that already exists in the Service SO, then the new text set will be created.

5) Create a new service sales order – text at both notes id and service agreement level are not added. No text is created in the order.

Changes have been implemented to recognize the ‘blank’ setting in Y/N fields for the following Item related panels accessed via Work with forward maintenance proposals, New values:

• DMR00804
• DMR00404
• DMR01004
• DMR006
• DSR001
• PHDR062

• When the package type is changed the related dimensions like length, width and height are now updated.
• A new Accumulate weight/volume button on each package creation form has been added. When this button is pressed then the weight and volume will be recalculated based on order lines packed and the package type selected during packaging.

1. Mandatory Grouping Code and Grouping Category

• The previously optional Grouping Code and Grouping Category are now mandatory.
• These attributes are now linked to the Chart of Accounts.
• For each main account part, a Grouping Code (SAF-T account code) and a Grouping Category must be specified.

2. UI Enhancements: Improved Naming for Clarity

• Menu options, panel labels, and field names have been updated for better clarity.
• The term “Std Account Code” has been renamed to “SAF-T Account Code(s)” across the interface.

3. Postal Code Field Made Optional

• The <PostalCode> element under <Header><Company><Address><City><PostalCode> in the header file structure, customer file, and supplier file structure in XML is now optional.

4. Business partner Accounts Consolidation

• If a business partner has two main accounts, they will now be reported under the same business partner section in XML.
• Previously, these accounts were listed in separate sections.
• The relevant reports have been updated accordingly, as detailed in the installation instructions.

5. Addition of New XML Tags
Two new tags have been introduced in the XML structure:

• Voucher Type
• Voucher Number

6. Updated Journal Type Labels in XML
The fixed journal type values have been replaced with more descriptive labels:

• “A” is now “Assorted Journals”
• “GL” is now “General Ledger Journals”
• “AR” is now “Accounts Receivable Journals”
• “AP” is now “Accounts Payable Journals”

7. Replacement of <TaxAmount> in XML
The <TaxAmount> element has been replaced with:

• <DebitTaxAmount> – Used when the amount is greater than or equal to zero.
• <CreditTaxAmount> – Used when the amount is less than zero.

8. Standard VAT Code Now Mandatory
The Standard VAT Code field, which was previously optional, is now mandatory as per SAF-T Version 1.3 requirements.

The following has been implemented:

1. New SENDGRID (Alert emails using Sendgrid) Function control. This simplifies configuration and does not require changing the AMT setup. If this function control is active this method will be used over SNDDST.
2. New default and replacement for setting up required configuration to use API.

• Group SENDGRID (Sendgrid configuration)

The following key values need to be set up:

ACCESS TOKEN1 – To define bearer token
ACCESS TOKEN2 – continue bearer token if exceeds 50 characters
ACCESS TOKEN3 – continue bearer token if exceeds 100 characters

FROM ID1 – To define from email id
FROM ID2 – continue from email if exceeds 50 characters
URL1 – To define URL
URL2 – continue URL if exceeds 50 characters

SRODESADV1/2/3/5/6

When a MDC sales order is created in the Demanding company, the sales price (available discounts, VAT% = Net price) is retrieved from the Supplying company and the same retrieved price is used as the purchase price at the time of purchase order line creation.

When the PO is created, the system sends the same purchase price to the Supplying company as the sales price.

For the MDC sales order, the system calculated the wrong sales price in the Supplying company due to VAT include price = Y. During the sales order line creation in the Supplying company, the VAT calculation erroneously took place again on the received sales price. The system kept breaking the calculated amounts during the sales order line creation process; then in pick confirmation; and subsequently in other programs like during invoicing. This resulted in incorrect prices during the processing of order entry, picking and other programs.

Logic has been modified to work correctly when VAT is included in the prices.

The following informational message will now be displayed during order exit if the customer on the order has the Peppol DI method active and the order is set up for merge invoicing.

Message:

Information: Peppol e-invoice interface record will not be created <HELP> Merge invoice is active on the order. Interface record is not created for merge invoices during invoicing.

The new default sequence by Date in descending order is applicable for both loading methods (i.e., using the database files and via the SQL query (More selections)). The Date column has been moved to the first column.

Information: Serial number reservations exist on the pick list <HELP>

LOCVATRG (Use local VAT registration for seller/trader country retrieval).

Activating this function control would apply in the following scenarios:

1) If System company (seller) is creating direct delivery sales order outside of EU from the supplier (which is located in another EU country), where System company (seller) has VAT registration – then Trader country will be populated as Supplier’s country.

2) If System company (seller) is creating direct delivery sales order outside of EU from the supplier (which is located in another EU country), where System company (seller) does not have VAT registration – then Trader country will be populated as Seller country.

If this function control is not activated, then the process will behave as it works today in standard, i.e., using Seller country as Trader country.

– Total VAT reg number other goods
– Total debtor country other goods
– Grand total other goods

– Work with A/P Payment proposals
– Journal maintenance
– Work with Journals in error / A/R invoices / Invalid transactions

An issue was identified whereby the CAMT054 file contained incorrect exchange rates. To address this, the programs have been updated to derive the exchange rate based on the system currency amount and transaction amount. The corrected exchange rate is now consistently used for all subsequent processing within the program.

For easier identification of the user who locked the order, the Username for the User ID has been added as a second level message as follows:

Message Description. This order is locked by <USER ID> <HELP>
Second Level…. Can only be unlocked by <USER Name> or an administrator.

To facilitate the identification of the produced serial number from an originating manufacturing order, the following enhancements have been implemented:

1) Serial number tracking enquiry:

– A Manufacturing order field has been added which will display the manufacturing order information. The existing Purchase order field will now only display the purchase order information.

– The Purchase order field on the More selections panel has been renamed to Purchase/Manufacturing order.

2) Work with manufacturing orders and Manufacturing order enquiry:

– A Serial number tracking option has been added which will access the Serial number tracking enquiry allowing you to track serial number items for manufacturing orders. If the selected item is not a serial number item, an error message will be displayed denoting that, ‘Item is not a serial number item’.

– Item
– Warehouse
– Date

The following columns, that can be activated via the Edit columns functionality, have also been added to the Manufacturing order enquiry, Inventory transactions panel:

– Item
– Description
– Batch number

DKOVHC (part of TABLE DI document) – GD131

DKOSACT (part of TABLE DI document) – DKF224

DKOSVCT (part of TABLE DI document) – DKF223

DKOKTO (part of ACCOUNT DI document) – GL010 ->Option 8

In the new 3.1 version information regarding Grouping Category and Grouping code is mandatory.

To comply with this legal requirement, the following has been implemented:

• New Grouping category code table (NOOGCAT) for maintenance of Grouping categories.
• New Grouping category field has been added on the Work with chart of accounts, SAF-T account code panel. This field is mandatory if the SAF-T account code field on the same panel is entered. The Grouping category attached to Chart of account is now printed on the standard audit file version SAF-T 1.3 standards.

One can now exit the panel if both fields are left blank.

If the SAF-T account code field is entered, then the Grouping category field is mandatory. If the Grouping category field is entered, then the SAF-T account code field is mandatory.

When the LOCVATRG (Use local VAT registration for seller/trader country retrieval) function control is activated, and the actual movement of goods for a Direct delivery order is within the EU; the Supplier country and Delivery country are not VAT registered at the Seller, then the following will take place:

• The Seller country will be set as the Trader country.
• If the Supplier country is VAT registered at the Seller, then the Supplier country will be set as Trader country

When the LOCVATRG (Use local VAT registration for seller/trader country retrieval) function control is not activated, then the Supplier country will be set as the Trader country even though the Supplier country is not VAT registered at the Seller.

– Customer/Debtor was not VAT registered for To-country (Delivery)

– To-country (Delivery) and From-country (Trader) were VAT registered at the Seller

The To-country (Delivery) was erroneously set as the From-country (Trader).

To facilitate the correct retrieval of the Trader country for such a scenario, the following now applies:

When the LOCVATRG (Use local VAT registration for seller/trader country retrieval) function control is activated, then the following will take place:

– The From-country will be set as the Trader country.

When the LOCVATRG (Use local VAT registration for seller/trader country retrieval) function control is not activated, then the following will take place:

– The To-country will be set as the Trader country.

To facilitate meeting legal requirements, the following has been introduced/applies:

• A Trader country field has been introduced on the Work with sales order, Order header, Main info panel. The same field is also available on the equivalent enquiry panel. This new field will only be displayed and available for update when there is any active line on the sales order.
• A Trader country column, that can be activated via the Edit columns functionality has been introduced on both the Work with sales order, Order header panel and Sales order enquiry, Order header panel.
• Upon changing the Trader country, the VAT handling codes applied on sales order lines and FEE level may get changed. As a result, order line and header values will be updated.
• Any change of the Trader country should be made as the last operation in the order cycle (e.g., any change to the delivery address, etc., should be made prior to manual update of Trader country).
• If any lines are added after manually updating the Trader country, then the manually entered trader country will be updated by system calculated value of the trader country. Hence it is recommended to update the trader country as the last step of the order.

UI_DC1UD User Data Entry

UI_SOE Sales Order Entry

These can be used to control usage of new user interface to sales order entry and non-critical data of users.

SM00072-“Debtor/Supplier country must be an EU member when Quarterly Sales List is produced”.

The error message has been changed to a warning message, if the LOCVATRG (Use local VAT registration for seller/trader country retrieval) function control is active.

If that function control is active, the system will check if the Debtor (Non-EU) country is VAT registered in the EU country and will issue a warning message if it is not.

In addition, the VAT registration retrieval process of the Debtor has been changed. For example: If the VAT registration number for Debtor (Non-EU) is not registered in the Business partner/Country VAT registration file (SRONCV), then the system will start reading all the records for Debtor in SRONCV. The first available VAT number with European Community member state = Y will be retrieved.

The system did not validate that the voucher date was within the transaction period for A/P transactions loaded from Medius interface files. This lack of check caused issues in EU VAT sales & Intrastat reporting because the voucher date was outside the transaction period and the invoice date was different from the G/L and VAT transaction dates.

A date control check has been added in the A/P invoice journal maintenance program to ensure the voucher date is within the transaction period.

Changes have been implemented in the back end to resolve the issue. A Confirmation window will automatically prompt, giving the user the possibility to unlock the batch, when the user tries to select an interrupted batch that was locked due to lost internet connection.

All checkbox fields on the Forward maintenance proposals, New values panels of the UI, for mass data update of Business partners and Items, have been changed to a 3-state field, i.e., Y, N and blank.

user,description,language,itemFileMaintenanceTemplate,busParFileMaintenanceTemplate

itemFileEnquiryTemplate,busPartnerFileEnquiryTemplate,defaultSalesOrderType,defaultPurchaseOrderType

defaultWorkOrderType,defaultQuotationOrderType,warehouse,handler,engineer

All these fields, except user name, could be updated by new update method.

Installation instructions:

– execute ‘Application preload tables update’

– update openAPI specification

– recreate api-bridge container

POM050GD

The following three new fields have been added with the amounts:

– Invoice plan

– Invoiced

– Remaining amount

POM050H

Changes have been implemented to decide whether the invoice is a final invoice or WIP invoice.

POM051A

New panel for final invoicing – similar to POM050D.

Management of Direct costs and WIP (Work In Progress)

The following prerequisites for Direct costs and WIP must be met to be able to view the related fields and information, and utilize the Direct costs and WIP handling:

• The new PRJWIPFI (Project WIP and Final Invoice – Phase level) Function control must be activated.
• The Invoice plan on phase field on the Project/Quotation type maintenance panel must be set to Y.

After last invoice plan invoicing, occurring costs are typically direct costs to the project. However, one can also control costs via WIP if there are special circumstances like, e.g., significant additional work to the project, which may require another final invoice and cost management via WIP.

To accommodate Cost management via WIP, the following new field has been added:

A WIP direct cost field in Project/Quotation type maintenance and equivalent enquiry program (only applicable for Projects). This is a Y/N field that is used to control the phase closing when the final invoice from the project phase level invoicing is generated. Indicate if occurring costs are direct costs to the project after last invoice plan invoicing.

The following have also been added on maintenance, enquiry panels and in extension files:

1. A WIP field, where possible values are Yes and No. This new field is on Phase level and Element line, Activity and Service level. This field can be used for a scenario where initial project costs go via WIP until the last project invoice plan invoicing, but everything after that including additional work is treated as direct costs.
2. A Final invoice field, where possible values are Yes and No. This new field is on Phase level and helps system and user to control the phase closing when the final invoice from the project phase level invoicing is generated. This field can be used for a scenario whereby final invoice has been invoiced and you need to be able to close phase even though there is an open element line.

Closing of Project Phases

Close of project phases can happen via two functions:

• Project Phase level invoice plan invoicing (new screen added as a modification)
• Work with project phases (from the DC1 standard screen)

Project phases will now be allowed to be closed in both functions even if there are open elements.

When the phase is closed (status 99), but the element is open, all the costs after closing the phase are treated as direct costs. Direct cost will use the same WIP generating accounting routines, but immediately releasing WIP with the same accounting routines as used when closing the phase.

Creation of new elements under closed phases is not allowed

Once the status of the phase moves to 99, the creation of new elements is not allowed.

If new elements are required, the elements must be entered to a (new or existing) phase that is in a status below 99.

Accounting

New modifications that are used for booking costs in WIP or as direct costs will use standard DC1 accounting routines (creation of transaction type-based transactions to General Ledger) but will work according to the new parameter (WIP Y/N) and phase status.

Project / Phase / Element Maintenance and Enquiry – Required Database Additions

New fields have been added to the DC1 database that will help those responsible for the Project directly see the key cost and invoicing related values of their Projects. The actual XT fields were added in Phase 2. See Project phase level invoicing and WIP, Task 4 below.

The Error message on a not created sales order will only be generated when the following is true:

Tme/mtrl = No; Acq type is 1 (issued from Warehouse), and Element status is less than 40

• Forecast View (Added in a previous QA/Jira
• Budget
• Change Orders
• Invoices

Project information, Phase

The following information is displayed (you click the Next button to view the next panels):

• Budget
• Change Orders

Project information, Element

The following information is displayed (you click the Next button to view the next panels):

• Budget
• Change Orders

The new Project information, Forecast view panel allows you to view the total of all the phases and all the phase elements. The system automatically calculates the values on this new panel based on Actual, Forecasted and Budgeted values.

• If the item should be copied, (i.e., the Item field is selected), then the item is retrieved from the selected phase (i.e., the phase copied from the project phase). (Note that this is how the system has worked, but the item selection was not available.)
• If the item should not be copied (i.e., the Item field is not selected), then the item is retrieved to the phase from the project type.

A Deselect option has been added on the Phase invoice plan, Invoicing panel allowing you to deselect a previously selected planned invoice.

A new Re-set option has been introduced in the Work with WMS transactions routine. This option is only applicable for records with a status equal to 8 (Cancel). When this option is used, a cancelled transaction will revert to status 7 (In error). The Retry option can then be used to process the transaction into DC1.

Firstly, the multiple Belcotax interface files were populated with the required information by running the Belcotax declaration for a specific year in DC1/Iptor.com.

Post population of the Interface files a Windows PC based application needed to be run to import the Belcotax declaration from the Interface files and convert it into XML format for a specific DC1 release and library.

This enhancement eliminates the usage of the PC based program and automates the creation of the output XML file. To achieve the automated output the following has been implemented:

1) The existing Belcotax program that creates multiple interface files has been modified to now write the data from the Interface files BEBBCTAX0, BEBBCTAX1, BEBBC28150, BEBBCTAX8 and BEBBCTAX9 into a new work file BEW0261.

2) The data populated in the work file BEW0261 is then converted into CSV format and stored at the IFS location defined for the IFS communicator type BELCOTAX.

3) The IFS folder is monitored by Interform using newly developed workflow which picks the CSV file and then converts the CSV input into XML output and stores it at a desired output location.

The process starts with the user adding from and to period on the “Create SAF-VAT return file” panel.

A series of programs will then be called to generate data in the SRT0610 work file based on the entered period. The final program will then be called which generates VAT return files and places them in the IFS.

From the IFS, with the Netlang connection, the data will be transferred to the relevant authorities.

In the new 3.1 version information regarding Grouping Category and Grouping code is mandatory.

To comply with this legal requirement, the following have been implemented:

• New Grouping category code table (DKOGCAT) for maintenance of Grouping categories.
• New Grouping category field has been added on the Work with chart of accounts>SAF-T account code panel. This field is mandatory if the SAF-T account code field on the same panel is entered. The Grouping category attached to Chart of account is now printed on the standard audit file version SAF-T 1.3 standards.

To facilitate a more proactive approach and thereby prevent transactions from ending up in Journals in error after the sales order has been invoiced, the following warning messages have been implemented:

1) During sales order entry a new warning message “Debtor VAT registration number is missing” will be displayed when the entered customer is missing the VAT registration number in the Business partner set-up, the Debtor country is an EU member, and EU reporting is active in the company.

2) During sales order Debtor address maintenance, a similar warning will be displayed if the VAT registration number is missing for the changed Debtor.

Warning will be displayed during interactive order entry only.

Newly added warning has been included in the “Work with message exception handling” routine to turn on/off the warning display.

Installation instructions
Run the fix program FIXR205901 or pre-load for DIS after installing the program changes to create entries in the message exception routine.

The PO confirmation API has been updated to include the following parameters:

– Dispatch date

– Price

– Price unit

– Confirmed unit

– Batches

The following new API’s have been created to handle batch maintenance on purchase order line level before reception:

GET: /purchaseOrders/{order}/lines/{orderLine}/batches
POST: /purchaseOrders/{order}/lines/{orderLine}/batches
GET: /purchaseOrders/{order}/lines/{orderLine}/batches/{batch}
PUT: /purchaseOrders/{order}/lines/{orderLine}/batches/{batch}
DELETE: /purchaseOrders/{order}/lines/{orderLine}/batches/{batch}

The API URL is as follows:

PUT: /purchaseOrders/{orderNumber}/lines/{orderLineNumber}/receptions

In addition, in the sales quotation print API method, handling of new document ‘closeQuotation’ has been added to close single quotation and optionally print ‘Sales quotation close’ list.

VATRGEUC (VAT reg at least in one EU cou)

For non-EU based customers, if the VAT registration number does not exist in the delivery-to country and the main VAT reg number is also blank at business partner level, then the system will check if the VATRGEUC function is active or not in the Function control file.

If the VATRGEUC function is active, then new processing will take place to check if the non-EU based customer has a VAT registration number in any other EU country(ies). If found, then the system will retrieve the VAT registration number defined at the 1st found EU country. If the VAT code is found, then the system will not override the To country. Based on the From – To country, between which actual physical movement happened, the VAT handling code will be retrieved.

If the VATRGEUC function is not activated OR the Customer is EU-based, then the processing will be as of today in standard.

DMR822 – Supplier Evaluation Analysis report
DMR618 – Inventory transaction list printout
DMR637 – Periodical Stock Valuation printout

The following work files are used:
SRW0618 – Inventory transaction list – work file
SRW0637 – Periodical stock valuation – work file
SRW0822 – Supplier evaluation analysis – work file

The following function controls have been introduced to override member names. This is an optional way to override created member names:
SRW0618
SRW0637
SRW0822

The following fields have been added to the G/L Easy Entry:

Period – this field will be defaulted with the accounting period of the batch.

VAT Handling Code – this code will automatically be retrieved by the system based on the VAT catalogue configuration defined in the Account table.

The system will automatically perform the VAT calculation and generate the corresponding G/L VAT accounting transactions for accounts designated as VAT-related.

a) Current integration for Automatic AP invoice matching is changed and is integrated with Nextway.

b) DC1 provides required master data PO and PO lines to Nextway.

c) DC1 receives process match document from Next and store them in DC1 ERP Interface Files SROLBA, SROLBAL and SROLBV.

d) DC1 runs the A/P invoice matching process

4) AcknowledgeMatchDocument is created and sent to Nextway after completion of matching process.

manufacturingOrdersNetworks.get
manufacturingOrdersPhantomitems.get
manufacturingOrdersOperations.get
manufacturingOrderHeader.reschedule

The following APIs have been changed:

itemBalance.get
itemBalances.get
manufacturingOrderHeaders.get
manufacturingOrderMaterials.get
purchaseOrderHeaders.get
purchaseOrderLine.get
purchaseOrderLines.get

OpenAPI specification has been updated.

manufacturingOrderOperation.reporting
manufacturingOrderOperation.reschedule

The following APIs have been changed:

item.get
item.upsert
items.get
itemWarehouse.get itemWarehouses.get
generalTextLine.get
generalTexts.get

When the DSPFCOST function control is not active, the Planned cost field will be displayed under the Budget, Planned values section as well as the Change orders, Planned values section as it was before this enhancement. The system will continue retrieving the ‘Budget Actual cost value and Change Actual cost as earlier.

When the DSPFCOST function control is activated, the Forecast cost field will be displayed under the Budget, Planned values section as well as the Change orders, Planned values section.

The value in the Forecast cost field will be as follows:

• On the Project information, Header panel, this Forecast cost field will display the value that was defined in the Forecast field on the Budget maintenance panel.
• On the Project information, Phase panel, this Forecast cost field will be left empty as the field value is reported only on project level.
• On the Project information, Element line panel, this Forecast cost field will be left empty as the field value is reported only on project level.

Mobwhs Put away and Replenishment processes did not support serial number handling. Under this enhancement, Serial number handling has been added for menus ‘Zone replenishment’, ‘Receiving location putaway’ and ‘Replenishment’.

Other related menus ‘Putaway’ and ‘Location putaway’ are not part of this enhancement.

The following JSON forms are changed:
1) nurfPickForReplenishment
2) nurfPutForPutAwayLocation
3) nurfPutForReplenishment
4) nurfPutForZoneReplenishment
5) nurfRecLocationPutAwayLines
6) nurfToZoneReplenishmentLines

There was a need, for internal use, in the WMS system to identify what units were used as the following:

– Basic UOM (Unit of Measure)
– Inner package
– Outer package
– Pallet layer
– Pallet

To accommodate this need, the following has been introduced:

– New WMS unit type field has been added on the Item file maintenance, Units panel where you enter the applicable WMS unit type. In the interface to the WMS, only the units that contain an entry in the new WMS unit type field will be included.

– New file SROPRUEX has been created to store the logistic unit in DC1. Trigger program has been modified to include new file.

– New field has been added in interface file SROSNDPRU

– New field has been included in the API response. /dataInterchangeTransmissions/items/{item}/units/{unit}
/dataInterchangeTransmissions/itemsUnits
New response element ‘wmsUnitType’ has been added.

Limitation:
CDM, Defaults & attributes, and Forward maintenance are not in the scope of this enhancement. Refer FDR on Jira for more details.

A new ‘IS’ transaction type has been created for the incoming inbound shipment (direction Send). It includes the following segments:

IBPS Business partner
IOAS Address
IODS Detail
IOHS Header
IOTS Text

-SROSNDLCH
-SROSNDLCL
-SROSNDPOH
-SROSNDPOA
-SROSNDPOT

New API’s have been created to get data from the new files
– SROSNDLCH and SROANDLCL
API URLs:

base/v1/iptor-erp-api-interfaces.json
/dataInterchangeTransmissions/inboundShipments/{shipment}
/dataInterchangeTransmissions/inboundShipments
/dataInterchangeTransmissions/inboundShipments/{shipment}/orders/{order}/lines/{orderLine}
/dataInterchangeTransmissions/inboundShipments/lines

API’s have been changed to include the newly added field in the responses.

Affected API(GET) method:

/dataInterchangeTransmissions/inboundShipments/lines
/dataInterchangeTransmissions/inboundShipments/{shipment}/orders/{orde r}/lines/{orderLine}

Following fields have been added in the response:
“salesOrder”
“salesOrderLine”

The bookkeeping system must support the submission of the annual report and by
> Generating a CSV-file with bookkeeping data which is accepted for upload in Regnskab Basis or to generate the data in XBRL-/iXBRL
format, which accepted for upload in Regnskab
Special Link below includes helpful information:
https://erhvervsstyrelsen.dk/vejledning-xbrl-og-inline-xbrl-rest-kl…
The annual report (Income Statement and Balance Sheet) details can be found in attached excel sheet ‘2023-01-31-Standardkontoplan+VAT’.

https://erhvervsstyrelsen.dk/vejledning-xbrl-og-inline-xbrl-rest-klient-eksempel-i-java

1) Renamed the PLDD014 panel title from “Internal stock transactions” to “Internal stock documents”.

2) Renamed the PLDD028 panel title to “Internal stock documents enquiry”.

3) Renamed document type field on both PLDD01404 and PLDD02604 to “Internal document type”.

4) Renamed Trans type field on both PLDD01404 and PLDD02804 to “Pickup/Reception”.

5) Renamed “Transaction number” field on both PLDD01404 and PLDD02804 panel to “Transaction type”.

6) Renamed the program title to “Internal Stock documents” for PLDR014.

7) Renamed the program title to “Internal Stock document enquiry” for PLDR028.

8)The menu item name for PLDR014 and PLDR028 have been changed to “Internal stock documents” and “Internal stock documents enquiry”.

9)The menu INVHAN has been modified to include the modified menu item PLD014.

10)The error messages PLD0102, PLD0116, PLD0117, PLD0120 and PLD0121 have been modified to say “Internal stock document” instead of “Internal stock transaction”.

11)The program overview and loading subroutine SR01 has been modified for both PLDR014 and PLDR028.

As part of this modification in PD standard the following has been done:

1. A new EINVOICE function control has been created
2. E-invoicing metadata placeholders have been established at both Default and Replacements and Business Partner level to store E-invoicing related metadata in Iptor.com
3. The Iptor invoicing routine has been modified to include the metadata defined in point 2 in the Iptor invoice xml i.e. DMR344JET
4. Many pre-validations have been added at different places to ensure that the user does not accidentally miss out on entering information which leads to errors during E-invoicing validation in Interform NG2
5. xsl transformations have been created to format the invoice related data from DMR344 to have proper date format, decimal separators and more that allows Interform NG2 to map invoice related data in PEPPOL format without using any translation tables in Interform NG2. These translations are stored within Interform NG2
6. Several templates have been created in Interform NG2 to map Iptor.com invoice data into PEPPOL E-invoicing format
7. The following new API endpoints have been created:

   -GET /businessPartners/{businessPartner}/searchAttributes

   -GET /businessPartners/{businessPartner}/searchAttributes/{template}

   -GET /businessPartners/{businessPartner}/addresses/{addressNumber}/searchAttributes

   -GET /businessPartners/{businessPartner}/addresses/{addressNumber}/searchAttributes/{template}

   -GET /businessPartners/{businessPartner}/e-invoiceConuntries/{country}/formats/{format}/keys

   -GET /businessPartners/{businessPartner}/e-invoiceConuntries/{country}/formats/{format}/keys/{key}

Changes have been implemented in program DSR500. During the execution of the Confirm full reception option then each reception note is validated. If a reception note fails validation, the system will now display the error messages with newly added error message ID DS50026. The user can skip processing that specific note and the system will continue processing the remaining valid reception notes.

• Ability to save XML files to IFS folder instead of transferring files via remote outqueue.
• Output folders are defined in Default&Replacement group OMG.
• Files are saved in IFS folders by direct job ASWOUT_*T of dataqueue routine ASWOUT.

GET /itemsOrderStructures

GET /items/{item}/orderStructures

POST /items/{item}/orderStructures

GET /items/{item}/orderStructures/{line}

PUT /items/{item}/orderStructures/{line}

DELETE /items/{item}/orderStructures/{line}

itemExtendedDescription.get

itemExtendedDescriptions.get

itemExtendedDescription.upsert

itemExtendedDescription.upsertctures

A new Inbound shipment form has been added under the Inbound menu.

When you select Inbound shipment a new Select inbound shipment form appears. It is possible to perform a live search on shipment and description.


When you select a shipment a new Receive purchase order line form appears. On this form the user can enter values in the applicable input fields, e.g., Rec location, PO number, Item, Quantity, etc. The system performs a validation for all input fields. After pressing the Update/Confirm key, the PO line will be received.

As previously mentioned, the following new forms have been created:

nurfSelectInboundShipment

nurfReceiveInboundShipmentLines

The following form has been changed:

nurfItemLabelPrint

• New fields have been added in the Service agreement header panel to store the buyer’s reference and your order information.
• These fields will be inherited to display buyer reference and your order on the Work with service orders/order line additional info panel for the attached agreement.
• The Invoice printout routine has been modified to print the buyer reference and your order in both Jetform and Portrait.

The following documents are attached on the Jira:

• FDR (Functional design)
• TDR (Technical design)
• UTR (Unit test results)

Interform layout has been updated to include the new fields.

If the WMSITVAL function control is activated, then a validation will be done to check if the warehouse used during new line addition in sales order or purchase order is active for WMS. If it is active, then the item will be activated for WMS if it is not already activated.


Existing default and replacement group “WMS-DYN” has been modified, and the following new level and key values have been introduced:


New level: ITEMINIT


New key: WMSINLO
Under the new key, item default for WM1 values should be defined


When a new sales/purchase order line is added for a WMS-active warehouse and the item has not been sent to WMS then the system will activate the item for WMS information if the following setup has been done:

• New function control is active
• Default item template is defined in the default and replacement new key
• Item template is valid and it is defined with validate fields as Y

1. The quantity should be immediately available in the reception area as soon as the quantity is reported

It is now possible to make the received quantity immediately available when the ‘PORECEPT’ function control is inactive and the WMS setup on warehouse level is to send PO in status 30.

2. It should be possible to consider the received quantity immediately as not available for sales.

It is now possible to assign the inventory status at the time of reception of purchase line event. New inventory status (inventoryStatus) field will be added as an optional field in the API request payload.
Stock will be allocated to received stock category (inventory status) after reception confirmation. IRO, BTB, and MDC PO lines will not be considered in the above processes.

3. Increase/Decrease some quantities from a Stock Category

To fulfil this requirement, a new *ADJSTS transactionEvent has been Introduced.

When a new event is received with positive quantity the system will internally add the requested quantity in the stock on-hand and then adjust the same quantity against the inventory status (Quantity type).

When a new event is received with negative quantity system will internally remove the requested quantity from inventory status (Quantity type) and then the same quantity will be removed from the stock on-hand. Quantity to remove must be available on the stock category.

4. Move some quantities between two different Stock Categories

To fulfil this requirement, a new *MOVSTS transactionEvent as well as a new ‘inventoryStatusNew’ element in the request payload of existing API have been introduced.

Upon receiving *MOVSTS the system will first perform a *RMVSTS transaction using ‘inventoryStatus’, if transaction is successful then *ADDSTS transaction will be performed using new element ‘inventoryStatusTo’.

Please refer Jira for Delivery concept, TDR documents.

The bookkeeping system must support the submission of the annual report and by Generating a CSV-file with bookkeeping data which is accepted for upload in Regnskab Basis or to generate the data in XBRL-/iXBRL format, which accepted for upload in Regnskab Special Link below includes helpful information: https://erhvervsstyrelsen.dk/vejledning-xbrl-og-inline-xbrl-rest-kl… The annual report (Income Statement and Balance Sheet) details can be found in attached excel sheet ‘2023-01-31-Standardkontoplan+VAT’.



https://erhvervsstyrelsen.dk/vejledning-xbrl-og-inline-xbrl-rest-klient-eksempel-i-java

1. Renamed the PLDD014 panel title from “Internal stock transactions” to “Internal stock documents”.

2. Renamed the PLDD028 panel title to “Internal stock documents enquiry”.

3. Renamed document type field on both PLDD01404 and PLDD02604 to “Internal document type”.

4. Renamed Trans type field on both PLDD01404 and PLDD02804 to “Pickup/Reception”.

5. Renamed “Transaction number” field on both PLDD01404 and PLDD02804 panel to “Transaction type”.

6. Renamed the program title to “Internal Stock documents” for PLDR014.

7. Renamed the program title to “Internal Stock document enquiry” for PLDR028.

8. The menu item name for PLDR014 and PLDR028 have been changed to “Internal stock documents” and “Internal stock documents enquiry”.

9. The menu INVHAN has been modified to include the modified menu item PLD014.

10. The error messages PLD0102, PLD0116, PLD0117, PLD0120 and PLD0121 have been modified to say “Internal stock document” instead of “Internal stock transaction”.

11. The program overview and loading subroutine SR01 has been modified for both PLDR014 and PLDR028.