{"id":32738,"date":"2026-10-27T10:18:06","date_gmt":"2026-10-27T10:18:06","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=32738"},"modified":"2026-10-27T10:18:06","modified_gmt":"2026-10-27T10:18:06","slug":"dynamic-project-code-extraction-in-automatic-journal-pih2","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2026\/10\/27\/dynamic-project-code-extraction-in-automatic-journal-pih2\/","title":{"rendered":"Dynamic Project Code Extraction in Automatic Journal (PIH2)"},"content":{"rendered":"\n

In Sage X3<\/a>, Automatic Journals are widely used to derive values dynamically during invoice posting. One common requirement is to extract the correct Project Code from the purchase invoice details line.<\/p>\n\n\n\n

New Stuff:<\/strong> Holiday Shipping Preparation in Sage X3 with GUMU™ ShipEazy<\/a><\/p>\n\n\n\n

Recently, a client faced a posting error on a purchase invoice. The issue was related to the formula used in the Automatic Journal (PIH2 \u2013 Identification Key).<\/p>\n\n\n\n

\"Purchase<\/a><\/center> \n
Purchase Invoice Posting Error<\/center><\/font>\n\n\n\n

In the Identification Key of the Automatic Journal, the following formula was already configured as a custom change as shown in below fig2.<\/p>\n\n\n\n

\"Automatic<\/a><\/center> \n
Automatic journal PIH2 Identification key<\/center><\/font>\n\n\n\n

This formula was extracting only the first 8 characters. However, this approach was not reliable and could not be continued.<\/p>\n\n\n\n

When the Project is added in the Automatic Journal line, we cannot directly put the project code. The system expects the value in a specific standard format. e.g ZME-INT-0030!CTC-003C<\/p>\n\n\n\n

In this format, the part before the \u201c!\u201d represents the actual Project Code (ZME-INT-0030), while the part after the \u201c!\u201d contains additional information.<\/p>\n\n\n\n

Because the length of the project code is not fixed and the value always contains the ! separator, using a fixed left$ formula was causing incorrect extraction and posting failures.<\/p>\n\n\n\n

To handle this dynamically, we created a reusable function that checks for the presence of the ! character and extracts the correct project code.<\/p>\n\n\n\n

If the project value contains \u201c!\u201d, extract everything before the first \u201c!\u201d as the actual Project Code. If there is no \u201c!\u201d, take the complete value as the Project Code. This ensures that the function works correctly for project codes of any length.<\/p>\n\n\n\n

\"Project<\/a><\/center> \n
Project extract function<\/center><\/font>\n\n\n\n

Please follow the steps given below :<\/p>\n\n\n\n

-Created the above function ZAPP.
-Compiled the script.(ZPJM).
-In the PIH2 Identification Key, replaced the old fixed formula – func ZPJM.ZAPP([F:PID]PJT)
-Attached the function so that the Automatic Journal now dynamically extracts the correct project code based on the standard ! separator format.<\/p>\n\n\n\n

\"Replace<\/a><\/center> \n
Replace Project Identification Key with Custom Project Function ZAPP<\/center><\/font>\n\n\n\n

By understanding the standard project format (XXXX!YYYY) and replacing the fixed-length formula with a dynamic function, we successfully resolved the posting issue and made the Automatic Journal configuration flexible for all project codes.<\/p>\n\n\n\n

About Us<\/strong><\/h2>\n\n\n\n

Greytrix \u2013 a globally recognized and one of the oldest Sage Development Partners is a one-stop solution provider for Sage ERP and Sage CRM organizational needs. Being acknowledged and rewarded for multi-man years of experience and expertise, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third-party add-on development, and implementation competence.<\/p>\n\n\n\n

Greytrix has some unique integration solutions developed for Sage CRM<\/a> with Sage ERPs namely Sage X3<\/a>, Sage Intacct<\/a>, Sage 100<\/a>, Sage 500<\/a>, and Sage 300<\/a>. We also offer best-in-class Sage ERP and Sage CRM customization and development services to Business Partners, End Users, and Sage PSG worldwide. Greytrix helps in the migration of Sage CRM from Salesforce | ACT! | SalesLogix | Goldmine | Sugar CRM | Maximizer. Our Sage CRM Product Suite includes addons like  Greytrix Business Manager, Sage CRM Project Manager, Sage CRM Resource Planner, Sage CRM Contract Manager, Sage CRM Event Manager, Sage CRM Budget Planner, Gmail Integration, Sage CRM Mobile Service Signature, Sage CRM CTI Framework.<\/p>\n\n\n\n

Greytrix is a recognized Sage Champion Partner for GUMU™ Sage X3 \u2013 Sage CRM integration listed on Sage Marketplace<\/a> and Sage CRM \u2013 Sage Intacct integration listed on Sage Intacct Marketplace<\/a>. The GUMU™ Cloud framework<\/a> by Greytrix forms the backbone of cloud integrations that are managed in real-time for the processing and execution of application programs at the click of a button.<\/p>\n\n\n\n

For more information on our integration solutions, please contact us at sage@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"

In Sage X3, Automatic Journals are widely used to derive values dynamically during invoice posting. One common requirement is to extract the correct Project Code from the purchase invoice details line. New Stuff: Holiday Shipping Preparation in Sage X3 with GUMU™ ShipEazy Recently, a client faced a posting error on a purchase invoice. The issue\u2026 Read More: Dynamic Project Code Extraction in Automatic Journal (PIH2) »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,13,8],"tags":[176,4744,4743,4745],"class_list":["post-32738","post","type-post","status-publish","format-standard","hentry","category-uncategorized","category-integration","category-sage-erp-x3","tag-automatic-journal","tag-project-code","tag-project-code-extract-function","tag-purchase-invoice-posting-error"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32738","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=32738"}],"version-history":[{"count":6,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32738\/revisions"}],"predecessor-version":[{"id":32744,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32738\/revisions\/32744"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=32738"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=32738"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=32738"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}