Transformation Rules in Celigo

Transform Rules is an integrator.io feature that helps you transform your large Export or Import JSON/XML data to a much smaller JSON structure that is much more readable and easier to understand. You can use this feature to: flatten the complex JSON structure. provide meaningful field names. select a limited set of fields for processing… Continue reading Transformation Rules in Celigo

Published
Categorized as Celigo

Celigo – HTTP Sucess response to Source in Webhook Export

Go to the Advanced Section in the webhook export where we can see the following fields. Override HTTP status code for the success responses: integrator.io returns a 204 HTTP status code for all successful webhook requests by default. Select an alternate successful HTTP status code for the listener. Override HTTP response body for success responses.… Continue reading Celigo – HTTP Sucess response to Source in Webhook Export

Populate Field values from source SO/Journal to Revenue Recognition journal

Revenue recognition journal will be created by bulk. So we can use map reduce script to populate the sublist value from source SO to revenue recognition journal.For the bulk processing, there may be chance for usage limit exceed issue and will throw an error “SSS_USAGE_LIMIT_EXCEEDED” and so you have to use the schedule script (scheduled/map… Continue reading Populate Field values from source SO/Journal to Revenue Recognition journal

Proposal For Colorado Delivery Fee in Sales order

Proposal summary  This proposal covers that adding the colorado delivery fee in the sales order based on the shipping address is Colorado and its proposed solution.  Requirement   When creating a sales order or open an existing sales order, before saving that SO we need to check whether the colorado delivery fee is added properly… Continue reading Proposal For Colorado Delivery Fee in Sales order

Revenue Management Process(ARM)

Revenue Management begins with the approval of a revenue source such as a sales order, cash sale,  return authorization, credit memo, cash refund, invoice, project, custom event, a subscription when  SuiteBilling is present, or a journal entry. From the approved transaction, a revenue arrangement  can be automatically created. Revenue arrangement is a transaction that represents a revenue contract. It contains the details  on how  revenue is going to be recognized. Revenue elements are attached as lines on a revenue  arrangement.  A revenue element represents a line on the source transaction. Each revenue  element has a forecast  revenue plan and one or more actual revenue plans that control the  posting of revenue.  Revenue recognition plans indicate the posting period that revenue  should be recognized, and the  amount to be recognized in each period. With multielement sales, the sales prices of the elements may not be the same as their fair value.  That’s when ARM uses revenue allocation. This process distributes revenue from a sale across  its elements in proportion to their fair value amounts. An actual revenue recognition plan is only created when a triggering event occurs. This could  happen  when the revenue arrangement is created, upon billing, fulfillment, or when a project  milestone occurs, and for certain events. The revenue recognition plans provide the information required to recognize revenue. The actual  revenue plans then become the basis for creating revenue recognition journal entries and revenue  reclassification journal entries during monthend processing. And NetSuite offers numerous reports  that help accurately analyze  forecast an actual  revenue.

Best Practices for script

General Scripting Guidelines Save retrieved values on a variable and use again on succeeding calls. Execute a block of code only if it satisfies a condition. Remove redundant operations or actions and lines of code which are no longer used within the script execution. Remove duplicate logic on a script that is already performed by… Continue reading Best Practices for script

Blank Columns in saved search formula results

Instead of zero, the saved search formula results in blank column values. This occurs because there may be null/blank values for any field used in the formula. The null/blank field values, when used in a formula result in null. This can be prevented by using the NVL function to replace null values with a quantity… Continue reading Blank Columns in saved search formula results