Ir al contenido principal

Subcontract Orders Without a Work Order

Subcontract orders are created to purchase one or more services from a supplier without having to set up and use the Sage X3 Manufacturing module (now called Sage Enterprise Management). Subcontract orders also allow tracking of components that come from stock and sent to a supplier along with components or material provided by the supplier. In this post we will illustrate creating subcontract orders without a work order in Sage X3.
Sage X3 Setup:
Purchasing subcontract parameters – EOM (Subcontract order management)
sage x3 sub-order
Purchasing subcontract parameters – ACC (Accounting Interface)
sage x3 sub-order
  • Activate Activity code LST – Subcontract deliveries
sage x3 sub-order
Supplier being sent the subcontract order will also need to be setup as a customer if components are being sent to the supplier.  This will facilitate subcontract shipments.
sage x3 sub-order
Create subcontract Location type and Locations.
sage x3 sub-order
sage x3 sub-order
Setup subcontract parameters on the Ship-to customer in Customers
sage x3 sub-order
Subcontract receipts require a transaction entry parameter with Subcontracting stock outputs set up as below
sage x3 sub-order
Modify allocation rule ALL08 (Setup>Stock>Allocation and issue rule) by setting the Location filter equal to “Local location” for Status “A”.
sage x3 sub-order
Add the allocation rule to Product categories associated with raw material or components shipped to subcontract suppliers. This is done on the Issue flow tab as indicated below.
sage x3 sub-order
Create a new Product category for service parts.
sage x3 sub-order
Create a subcontract service item.  Select the Subcontract Service category from above, and flag the item as Not managed and add supplier data as illustrated below.
sage x3 sub-order
sage x3 sub-order
Make sure the Accounting code associated with the new service part has the PO Clearing account in rows 1 and 41 – and a subcontract variance account in row 47
Set up a Subcontract BOM code.
sage x3 sub-order
Create a subcontract BOM.
sage x3 sub-order
sage x3 sub-order
Perform a standard cost calculation for the subcontracted product. Costing>Cost calculations>Standard cost calculation.  Make sure select the subcontract BOM type.
Create a new subcontract order.  Purchasing>Subcontract>Subcontract orders.
sage x3 sub-order
sage x3 sub-order
sage x3 sub-order
Click Order in the Specific actions menu on the right-hand panel and Order again to generate a subcontract PO.  A Log Reading will appear like the one below indicating the PO created for the subcontract order.
sage x3 sub-order
The raw materials can now be shipped to the Supplier.  Navigate to Sales>Deliveries>Deliveries and create a new delivery.  Be certain to use the Delivery type SDC for subcontract orders.  Your subcontract order will be in Subcontract shortage selection drawer in the Left list.
sage x3 sub-order
When the shipment is validated the stock is moved to the subcontract location assigned to the customer.  This happens automatically when setup properly. SUB01 below is the subcontract location assigned to customer.
sage x3 sub-order
After the supplier finishes the subcontract work they will return the subcontracted product entered on the subcontract order.  A Purchase Receipt (Purchasing>Receipts>Receipts) transaction will be executed to receive the product.
sage x3 sub-order
When the receipt is created the raw material is removed from the subcontract location and the subcontracted item is received into stock.
sage x3 sub-order
sage x3 sub-order
The Sub-contract order may now be closed. Navigate to Purchasing>Subcontract>Mass closing/completions.  Enter the Order site, Close (Mass closing/completions field), the subcontract order number and click OK.
sage x3 sub-order
The Mass closing/completions window will appear with the order to be closed checked. Click Close to close the subcontract order.
sage x3 sub-order
After the subcontract order is closed it must be costed.  Navigate to Costing>Subcontract cost>Calculate actual subcon. cost.  Enter the Receiving site, Order number and click OK.
sage x3 sub-order
A Log File for the subcontract actual cost calculation is displayed.
sage x3 sub-order
After the subcontract order is costed, the WIP accounting interface should be run. Navigate to Costing>WIP>WIP posting.  Enter the Production site, select the Entry type Subcontract order, select All Transactions and enter the order number then Click OK.
sage x3 sub-order
WIP posting will produce a Log Reading identifying the journal entry produced.
sage x3 sub-order
Note: This can be set up as a batch task.

Entradas populares de este blog

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...

Sage X3 Create a new CLOB Text

Here how to create a CLOB text Funprog F_CRELOB ( YABRFIC , YTEXTE ) Value Char YABRFIC Value Char YTEXTE Local Char XXRTFTXT ( 250 ) ( 3 ) XXRTFTXT ( 0 ) = "{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 MS Sans Serif;}}\viewkind4\uc1\pard\f0\fs17 " XXRTFTXT ( 1 ) = YTEXTE XXRTFTXT ( 2 ) = "\par}" Local Char X_RET Local Integer XXOK Local Char XCHAMPLIEN : XCHAMPLIEN = "YYYY" Global Char YYYY : YYYY = YABRFIC Local Clbfile WWCLOB Local Mask ACLOB [ M :ACL ] Setlob WWCLOB With XXRTFTXT [ M :ACL ] CLOB = WWCLOB Call CRE_CLOB_ACL ( XCHAMPLIEN , XXOK ) From TRTX3TEX Close Local Mask [ M :ACL ] X_RET = YYYY Kill YYYY End X_RET