S4HCKS43 – Generating a check digit on your invoice

A check digit to secure BPay payments

It may sometimes be necessary to add information to a document that is made up of other pieces of information (concatenate fields, truncate fields, transform fields, etc…) – that is, information that does not readily exist in your system (like a customer number for example), but can be generated or deduced.

In this snippet we look at how you can add some custom logic in your SAP S/4HANA Cloud system to generate a check digit to a BPay CRN (Customer Reference Number). That is, we want to offer our customer the BPay payment method and for that we have to add to the invoice a CRN number, that will be made of the billing document number appended by a check digit that we will generate on the fly in S/4.

The custom logic to generate the check digit

You will below find the custom logic that I used to generate this check digit (Disclaimer : my code is probably dirty – but it works). I am not checking the length of the billing document number – I have made the assumption that the billing number will always be 8 digits long.

I have also added a screenshot that shows how my custom ‘CheckDigit’ field was defined (Numerical – 1 digit).

* Logic to determine a check digit for a BPay 8 digit CRN number

DATA:
Counter       TYPE i,
lv_billdigit  TYPE i,
lv_total      TYPE i,
lv_billingdoc TYPE string,
lv_chardigit  TYPE string.

Counter = 0.
lv_billingdoc = billingdoc-billingdocument.
SHIFT lv_billingdoc LEFT DELETING LEADING '0'.

While Counter < 8.

   IF ( Counter MOD 2 = 0 ).
      lv_billdigit = lv_billingdoc+Counter(1) * 1 .
   ELSE.
      lv_billdigit = lv_billingdoc+Counter(1) * 2 .
   ENDIF.


   IF ( lv_billdigit > 9 ).
      lv_chardigit = lv_billdigit.
      lv_billdigit = ( lv_chardigit+0(1) ) + ( lv_chardigit+1(1) ).
   ENDIF.


   lv_total = lv_total + lv_billdigit.
   Counter = Counter + 1.
ENDWHILE.


IF ( lv_total MOD 10 = 0 ).
   billingdoc_extension_out-yy1_checkdigit_bdh = 0.
ELSE.
    billingdoc_extension_out-yy1_checkdigit_bdh = 10 - ( lv_total MOD 10 ).
ENDIF.

Video: Generate a - BPay - check digit on your invoices

BPay check tool for Excel

In case you are interested to have it, I am also adding the Excel file that I used to double check the check digit generation. The CRN numbers in the file and check digits were generated on the BPay generator web page. You can download the excel by clicking the icon below.


S4HCKS42 - SAP S/4HANA Cloud Scope Map Generator

A key piece of information  that I use in my interactions with customers, is the SAP S/4HANA Cloud Best Practice practices content, for which I am sure you have already heard the term scope item. If not then head on out to the Best Practices Explorer for SAP S/4HANA Cloud portal (note you need to log on with your S-User to access the rich library of accelerators). To be more specific, I like to use a graphical view of our best practices, because I find that a picture really does paint a thousand words. It is a great conversation piece that I use before, during and after a project.

However, with the ever increasing number of scope items and country localisations that come with every new quarterly release of SAP S/4HANA Cloud, trying to build a graphical view of a scope map becomes a tedious and time consuming task. What’s more when I talk to my customers, I want to provide them with content that is specific to them : Show them a scope map of those scope items that apply to them, for their chosen country localisation(s) and/or presented in such a way that lets them take in what they are using, yet also, more subtly shows what is available to consume if and when they will have the need for additional functionality.

Furthermore, a scope item may not be released in all countries – for example there are some statutory reporting capabilities that are specific to a country. There is no added value for my Japanese customer to know that the US 1099 tax reporting is not available for country Japan. Again, the idea is to offer something that is personalised to the customer.

With that in mind, not wanting to become an Excel or Powerpoint jockey, I decided to come up with a tool that would help me in this task of producing customer specific Best Practices Scope maps. That said, the tool could also be used by partners during their engagements with customers to for example highlight specific services or know-how that they have in certain areas, or customers themselves to for example help them keep track of their used scope and / or build future state roadmaps.

This tool is an Excel based tool that will produce Scope Items maps in Excel and, optionally can also generate a set of Powerpoint slides, if you needed to wrap them up nicely in a presentation. In Excel, there will be one worksheet generated for each business area selected, and in Powerpoint there will be one slide for each scope item group as well as one slide per business area. And example of both these displays is shown below.

Excel Output

Powerpoint Output

Generating a scope map

Before you start

Once you download the zip archive and unpack it, you should have two files. An Excel document (this is the core file), as well as a Powerpoint template file named “Template.potm”. This is a blank Powerpoint Template file that will be used when you generate your personalized scope map. You can use your own template (with your own company colours and formatting) if you wish to. TO do so place your own temaplte file in the same folder as the excel document, and name your template”Template.potm” because that is hard coded in the macro – that is the name and place it looks for it.

Also, I would recommend that you do not execute the macro whist the documents are stored in a dropbox or onedrive folder location especially if you have a less than optimal bandwidth. I have found that trying to run the macro as well as update the file live in such a network folder leads to periods of – long –  unresponsiveness.

Getting Started : Selection Screen

The first thing that you will need to do is decide whether you want to see a generated scope map independent of a country localisation, or on the contrary you want it specific to a country. The main difference between these two selections is that the country specific map will grey out those scope item that are not available in the chosen country.

The map can only be generated for one country at a time.

The next thing you will need to do is select one or more business areas for which the scope map should be generated. For each of the presented business areas, simply click the corresponding selection box to include it in the generated scope map.

Choosing Display Criterias

For each scope item that is determined, based on the business areas you have chosen, one box will be displayed in the scope map. The box will include the scope item ID as well as the scope item description. There are then up to seven additional criteria that can be used to represent a specific feature, applicable to the scope item. For example, the content provided with the file will include information pertaining to a scope item being 2 Tier relevant, or it being an integration scenario. You may choose to use one criteria to represent a specific value driver, or a to highlight th fact that you have done some custom code extension or developed a side by side extensibility for this scope item, etc… The choice is yours. You can of course also re-purpose the delivered content. 2 Tier does not apply to you, use that criteria for something else more pertinent to you or your customer.

Each one of the selected criteria will then appear in the scope item box in the form of a Glyph. If you ask to generate a powerpoint deck as well, the first slide added to the presentation will be a legend slide to let the audience know the meaning of each glyph. That said if you want to use something else to represent each of these criteria (for example you want to see 2T instead of green circle to represent that the scope item applies for a 2 Tier scenario – the code is freely accessible you can change this)

Generating a Powerpoint presentation deck

If you also want to generate a Powerpoint slide deck of your chosen business areas, in addition to the information generated in Excel, then simply select the ‘Generate Powerpoint’ checkbox in the Other Options section. Then, in addition to this you can elect to generate the Powerpoint content as pictures or html tables. The essential difference between these two options, is that the picture will be a static element that cannot be changed, whereas the html table option will generate objects that are fully editable in Powerpoint (for example you want to color some scope items in red).

Video: Scope Builder

Downloading the required files

To download the needed files, simply click on the icon to the right !

Updated with 1905 content – 20 June 2019

FAQ

There is no fee associated with the use of this tool.

If you do use it, I would appreciate that you subscribe to the SAP S/4HANA CLoud Knowledge Youtube Channel and spread the word on social media.

If you would like to make a monetary donation, then I would ask that you make a charitable donation to an organisation that helps with raising dyslexia awareness such as  MSL Club in Australia or The Reading League in the USA.

Before you ask, no you cannot charge for this tool.

To change the criterias that appear for each scope item:

  1. Go to the tab named “SETUP”.
  2. In the section “Output Criteria – Explanation”, in the column named “Significance” change the name of one of the free criterias (named Criteria 4, 5, etc…) to the name you want to give to it
  3. Go to the tab named “DATA”
  4. Columns L to O map to the free criterias (Criteria 4 –> Column L, Criteria 5 –> Column M, etc…). At the intersection of your criteria and scope item ID, put an ‘X’ in the cell if your criteria applies. NOTE : It has to be an X – anything else will not be taken into account.

If you want to use your own template, then create your own .potm file in Powerpoint, with the look and feel you want to give it (colours, fonts, logo…). Then save that file in the same folder where you have saved the Excel file, and name it “Template.potm”. The macro looks for a file with that exact name, in the same folder as the excel document.

Yes, you can use the generated output for your S/4HANA Cloud Projects. But note that this tool is not created, provided, endorsed or supported by SAP. If you use it, then you are responsible for checking the accuracy and veracity of the data that you will generate and use.

Yes, you sure can ! The code is available and open. You will also note that my code is fairly “dirty”. If you do find a way to optimise the code or correct a bug or add a new features to it, then please send me an updated version of the excel document, so that I can update the source file and the entire community can benefit from this !

Yes – absolutely.

A well thought out critique is worth Gold (E.Musk). Any feedback as long as it is not offensive is welcome, good or bad. You can leave a comment here or on the video on YouTube.


S4HCKS41 - Execute Capacity Levelling in SAP S/4HANA Cloud

In this snippet we show you how to level your production capacity, to avoid bottleneck situations or if you want to plan your manufacturing operations on the basis of cadence setting work centers.

Importantly, make sure you check out the following links:


S4HCKS40 - Create MRP Areas from Excel by leveraging API's

In this snippet we re-visit a previously released snippet : S4HCKS23 Mass Processing Product Master changes in SAP S/4HANA Cloud, but this time leveraging an API that is called from the comfort of MS Excel.

The underlying objective of this snippet, is to show how easy it is to leverage our API’s from third party applications, not just in Read mode, but also in Create/Update Modes. In this snippet we show you how you can supplement your Product Masters with MRP Areas, but this coud apply to any other of the available API’s.

As indicated in the recording, I am providing the excel used in the recording, for you to try out and get some inspiration from. As a disclaimer : You can use it at your own risk – I take no responsibility for you using it. I encourage to first try it in your Q system, with a small dataset. I also remind you not to pass this file to others with either data and / or login credentials !

Some of the important links covered in the recording are:

I must also give credit to Philip Hoffmann, who’s blog provided the file that I have also used to kick start this project. Phillip’s blog also covers how to create a communication user.

I encourage you to read the ‘Read Me First’ tab to get some valuable information, but if you want to just dive right in after you have created your communication user, then you just need to maintain the data you want to upload (MRP_RECORDS tab) and the login credentials as shown below (in the EXEC_DATA tab)

You can download my MRP Areas Excel API file below, by clicking the Excel File icon.


S4HCKS39 Tailor the AVC sales order UI down to a T

In this snippet we show you how easily you can continue to tailor the AVC sales order entry UI to make it work for you, using the SCREEN_DEP object.

Video: Tailor the AVC sales order UI down to a T


S4HCKS38 Easily setup your AVC pricing without any dependencies or code

In this snippet we show you how easily your AVC pricing could be setup, without using any dependency or code. Please check the video and note the restrictions under which this is possible.

Video: Easily setup your AVC pricing without any dependencies or code


S4HCKS37 Use the situation handling framework to identify and act on unwanted purchase orders

We live in an ever changing world. Juggling several responsibilities at once, it becomes difficult to stay on top of things. Customers cancel sales orders or change their orders, manufacturing cancels production runs or change the schedules, marketing decides that some products are no longer sold/manufactured. But you have already issued purchase orders to your suppliers to cover these requirements. So how do you know that some purchase orders may no longer be needed? What can you do to prevent purchasing products that you will no longer need and that will only take the dust in your warehouse? in 1902, with SAP S/4HANA Cloud, this has now becomes child’s play. You can now leverage the Situation Handling Framework, and let the system do the hard yards of finding those purchase orders that will drag the financial earth of your organisation south. In this snippet, we show you exactly how easy it is to leverage this new functionality.

Video: Leverage the Situation Handling framework to identify unwanted purchase orders


S4HCKS36 Use custom logic to determine your delivery pick locations

In this snippet we show you how you can easily and simply leverage custom logic inside SAP S/4HANA Cloud to embed a customised logic to determine the picking storage locations that are determined during delivery processing. The use case in this snippet looks at the delivery creation in the context of a subcontracted purchase order, i.e when you ship component to your suppliers.

Video: Use custom logic to determine your delivery picking locations


S4HCKS34 Manage your production capacity effectively

In this SAP S/4HANA Cloud Knowledge Snippet – #S4HCKS – we do a deep dive into a new Fiori Application that was released with SAP S/4HANA Cloud 1808. The app in question is Manage Work Center Capacity. You can find more information about this application in the Fiori Apps Library by following this link. You can also check out the application documentation here. If you are unsure where to start to begin exploring this application your self, then Best Practices scope item 31L – Production Capacity Planning and Evaluation– is a good start.

I will let you follow the video for a detailed walkthrough of you need to do in SAP S/4HANA Cloud to be able to fully leverage this application, but before that I will just offer a few pointers, that are also discussed in the recording .

Generate capacity requirements for planned orders

This is not a must and really depends on your situation – i.e is capacity an issue and are you always juggling with the capacity of your bottleneck or key work stations. If so, then you may wish to generate capacity requirements for your planned orders already coming out of MRP, so that you have visibility over the capacity requirement of your production plan over a longer horizon, then that just provided just by the production orders (which you would have only created when needed !).

If so, then you will want to execute the scheduled MRP run, with the scheduling setting ‘2’ – Detailed scheduling. This will have the effect of reading the product’s routing and not not the in-house production lead time in the material! Because you are reading the routing, it means that you are reading the routing’s work centres.

Is your formula enabled to generate capacity requirements?

The formula you will choose in the work centre (or create yourself) is very important, in that, if you miss the setting that will generate a capacity requirement, then you will not see any capacity in the capacity monitoring application! So make sure the ‘WKCtr for rqmts’ check box is active for your selected formula!

Tailor the system to your needs

It may be that you need to create your own formulas, to calculate the capacity requirements of your work centers using a specific formula. No problem, with SAP S/4HANA Cloud you can do that! Just head over the to the Manage your solution application, look for the SSCUI’s in the context Manufacturing / Shop Floor Control / Work Center and create your own formulas.

If you enjoy this post, please consider subscribing to our youtube channel and follow the hashtag #S4HCKS on twitter.

Video: Manage your production capacity effectively


S4HCKS29 Real World solutions with S/4HANA Cloud to real World problems

The stated requirement was to be able to have a KPI tile in the Fiori Launch Pad, that would show a count of the customers that had been able to reach one of two (or both) sales tiers. A sales tier being a sales volume. The numbers are not realistic, but let’s say that tier 1 would represent customers that had been able to reach a sales volume of 1000USD and tier 2 would represent customers that had been able to reach a sales volume of 2000USD. This volume had to be reached over a specific period of time, and if the customer reached one of the two tiers, over that specified period of time, he would then be eligible for a credit (or a rebate if you prefer). The higher the tier achieved, the greater the credit issued. As you can see, using standard features of S/4HANA Cloud, this was achieved quite easily.

The next requirement, was to be able to drill down to a graphical representation of these sales volumes and clearly highlight the two sales tiers (1000USD and 2000USD), so as to be able to instantaneously visualise which customer had reached these tiers. Again, as you can see below, this and much more was achieved using standard capabilities of S/4HANA Cloud. Not only were we able to build the desired graphical representation of the sales volumes and sales tiers, we also added mini charts (mini KPI’s) as well as various evaluations, so as to be able to slice and dice the information in various ways.

So far, the customer brief was met. However, thinking about the use of this data, it quickly becomes evident that the next steps to be taken on the basis of this data, is to be able to issue the due credit to the eligible customers – but how are you going to do it? From the app above, it is possible to present the data in tabular form, you could even add calculated fields in the evaluation of your KPI tile to calculate things such as the amount of the credit. You could also export the data to a spreadsheet and there also calculate the credit due. Then, you are left with the need to create the credit memo in the system. Whilst of course possible, this is fraught with risks (badly slicing the data could lead to over/under issuing credits) and of course immensely tedious – imagine someone entering a large amount of documents in the system manually (again fraught with risks). That said, thanks to S/4HANA Cloud and the power of extensibility there is a much better, faster and leaner way to do this.

What we did, was to use the ‘Custom Business Object’ in S/4HANA Cloud to define a new object – Sales Volumes tiers. The custom business object allows you to define the structure of the object that you need as well as the fields that define this object. In our case we needed fields that would pertain to customers, (customer ID, name, sales organisation…), tiers information (the volume that needed to be achieved as well as the % of the credit that would be issued). Lastly we also wanted to restrict how the volume was going to be measured. I.e was all the customer’s business going to count, or did we want to restrict by a set of materials or materials groups for example. We chose the material group. A snapshot of part of the structure of our Custom Business Object is shown below.

Once the custom business object was created, we then used some coding to realise the magic of the process, namely, to call a CDS to sum the amounts billed to the customer, and on the basis of that determine the amount of the credit to be issued to the customer (if eligible). Then we perform a second call to a whitelisted API to actually create the credit to the customer.

I will let you watch the video recording below to give you a complete view of what we did, but at a high level, in bullet point form below are the main steps/functions:

Creates a custom business object with the required structure and fields.
We added validation logic to make sure the data entered was correct, as expected and was going to play nicely with the subsequent processes
We added some logic, to call the CDS I_BillingDocumentItemCube so as to sum the sales volume of the considered customer.
One the basis of the sales volume determined, and based on the sales targets of the customer, we determine if the customer achieved the Tier 1 or Tier 2 target and if he did, we calculate the corresponding amount of the credit he earned.
We then make a POST call to the whitelisted API API_CREDIT_MEMO_REQUEST_SRV, to actually create the credit memo in the S/4HANA Cloud system.
Looking at these steps, you can imagine the level of automation that was achieved as well as the added value offered!

Video: Real World solutions with S/4HANA Cloud to real World problems


Code Snippets & how-to's

Please check out the blog from my colleague Arun here : https://blogs.sap.com/2018/06/13/mass-update-using-sap-s4hana-cloud-in-app-extensibility/ . His blog will show you what you need to do to setup the required communication arrangements. I would like to thank Arun for his wonderful blog which provided the missing pieces to mine as well as his pointers along the way.

All code provided below is provided as-is. You take full responsibility for using as it nowhere near production grade code.

Below is the code for the first action. It retrieves the sales volumes from the billing CDS and works out the credit due to the customer.

 

* Action Calculate for Node ID sales_volume_rebate
*
* Importing Parameter : association (Navigation to Parent/Child/Associated Node Instances)
* Changing Parameter : sales_volume_rebate (Current Node Data)
* Exporting Parameter : message (Message with Severity S(uccess), W(arning), E(rror))

* -----------------------------------------------------------------------
* calculate bonus
*
DATA: netamount TYPE P DECIMALS 2.
DATA: internetamount TYPE P DECIMALS 2.
DATA: bonus1 TYPE P DECIMALS 2.
DATA: bonus2 TYPE P DECIMALS 2.

IF salesvolumestiers-releasestatus GT '2'.
IF salesvolumestiers-isconsistent = abap_true.

" calculate product bonus
DATA: products TYPE TABLE OF i_productgroup.
DATA: product LIKE LINE OF products.

* get product list from sub node Products
DATA(bonusproducts) = association->to_materialgroups( ).

" get net amount for product
LOOP AT bonusproducts INTO DATA(bonusproduct).
SELECT *
FROM i_productgroup
INTO @product
WHERE i_productgroup~materialgroup = @bonusproduct-materialgroups-materialgroupid.
ENDSELECT.

SELECT
FROM I_BillingDocumentItemCube( p_exchangeratetype = 'M', p_displaycurrency = 'USD' )
FIELDS SUM( SlsVolumeNetAmtInDspCrcy )
WHERE creationdate BETWEEN @salesvolumestiers-validfrom AND @salesvolumestiers-validto
AND SalesOrganization = @salesvolumestiers-salesorg
AND soldtoparty = @salesvolumestiers-soldtoparty
AND materialgroup = @bonusproduct-materialgroups-materialgroupid
INTO @internetamount.

netamount = internetamount + netamount.

ENDLOOP.

salesvolumestiers-volumeachieved_v = netamount.
salesvolumestiers-volumeachieved_c = 'USD'.

if netamount LT salesvolumestiers-targetrevenue1_v.
salesvolumestiers-calculatedbonus_v = 0.
elseif netamount GT salesvolumestiers-targetrevenue2_v.
salesvolumestiers-calculatedbonus_v = ( ( netamount / 100 ) * ( salesvolumestiers-bonusrate2 ) ).
salesvolumestiers-calculatedbonus_c = 'USD'.
else.
salesvolumestiers-calculatedbonus_v = ( ( netamount / 100 ) * ( salesvolumestiers-bonusrate1 ) ).
salesvolumestiers-calculatedbonus_c = 'USD'.
endif.

salesvolumestiers-releasestatus = 4.

ENDIF.
ENDIF.
* SAP CODE BELOW

message = VALUE #(
severity = co_severity-success
text = 'Action CalculateCustomerCredit executed'
).

Then the next piece of code is that which is used create the credit memo per se. Again you will want (have to!) add your own error handling code and execution logic.

* Action CreateCreditMemo for Node ID SALESVOLUMESTIERS
*
* Importing Parameter : association (Navigation to Parent/Child/Associated Node Instances)
* write (API for creating and updating Custom Business Object Node Instances)
* Changing Parameter : SALESVOLUMESTIERS (Current Node Data)
* Exporting Parameter : message (Message with Severity S(uccess), W(arning), E(rror))

CHECK cl_ble_http_client=>is_service_available(
communication_scenario = 'YY1_INT_HTTP'
outbound_service = 'YY1_INT_HTTP_REST'
) = abap_true.

DATA(lo_client) = cl_ble_http_client=>create(
communication_scenario = 'YY1_INT_HTTP'
outbound_service = 'YY1_INT_HTTP_REST'
).

* we get the csrf token to be able to make the POST call later
DATA(request) = cl_ble_http_request=>create( ).
DATA lv_s2 TYPE string VALUE '/API_CREDIT_MEMO_REQUEST_SRV/A_CreditMemoRequest?%24top=1&%24format=json'.
request->set_header_parameter( exporting name = 'X-CSRF-TOKEN' value = 'FETCH' ).
request->set_method( 'GET' )->set_resource_extension( lv_s2 ).
TRY .
DATA(response) = lo_client->send( request ).
DATA(lv_csrf) = response->get_header_parameter( 'x-csrf-token' ).
CATCH cx_ble_http_exception INTO DATA(l5).
ENDTRY.

* We build the payload that will be submitted in the POST call
* We will also convert the calculated bonus to a string so that the call plays nicely
DATA: lv_payload TYPE string,
calcbonus TYPE string,
lv_pl41 TYPE string value '{"d" : { "PurchaseOrderByCustomer": "CREDIT-2018- ',
lv_pl42 TYPE string value '","SoldToParty": "',
lv_pl43 TYPE string value '","SalesOrganization":"',
lv_pl44 TYPE string value '","CreditMemoRequestType":"CR","OrganizationDivision":"00","DistributionChannel":"10",',
lv_pl45 TYPE string value '"to_Item": [ { "Material": "CREDIT","RequestedQuantity": "1","to_PricingElement": [ {',
lv_pl46 TYPE string value '"ConditionType":"PPR0","ConditionRateValue": "',
lv_pl47 TYPE string value '","ConditionCurrency":"',
lv_pl48 TYPE string value '"} ] } ] } }'.

* We retrieve the calculated bonus from the custom business object
calcbonus = salesvolumestiers-calculatedbonus_v.
* We get rid of the trailing space that is added to the calculated bonus
CONDENSE calcbonus.

* we concatenate the various fields that will make up the payload
CONCATENATE lv_pl41 salesvolumestiers-soldtoparty lv_pl42 salesvolumestiers-soldtoparty lv_pl43
salesvolumestiers-salesorg lv_pl44 lv_pl45 lv_pl46
calcbonus lv_pl47
salesvolumestiers-calculatedbonus_c lv_pl48 INTO lv_payload.

* we make the POST call to the credit memo request API
DATA(request1) = cl_ble_http_request=>create( ).
DATA lv_s1 TYPE string VALUE '/API_CREDIT_MEMO_REQUEST_SRV/A_CreditMemoRequest'.
request1->set_header_parameter( exporting name = 'x-csrf-token' value = lv_csrf ).
request1->set_content_type( 'application/json' ).
request1->set_method( 'POST' )->set_resource_extension( lv_s1 ).
request1->set_body( lv_payload ).

TRY .
DATA(response1) = lo_client->send( request1 ).
CATCH cx_ble_http_exception INTO DATA(lx1).
ENDTRY.

* We also want to be able to update the custom business object with the created credit memo number
* So we will use regular expressions to find the content of the tag in the response
DATA result TYPE match_result_tab.
DATA line LIKE LINE OF result.
DATA sub TYPE submatch_result.
DATA output TYPE string.
DATA lx60 TYPE string.
output = response1->get_body( ).

FIND ALL OCCURRENCES OF REGEX '((?:[^<]| LOOP AT result INTO line.
LOOP AT line-submatches INTO sub.
lx60 = output+sub-offset(sub-length).
ENDLOOP.
ENDLOOP.

* We update the custom business object field Credit Memo with the credit memo number just created
salesvolumestiers-creditmemo = lx60.

message = VALUE #(
severity = co_severity-success
text = 'Credit Memo Created:'
&& lx60
).

Share on Social Media