•May 30, 2013 • Leave a Comment
When working with SAP invoice SmartForms, you will soon become familiar with the LBBIL_INVOICE structure. The print driver program populates this deep structure with lots of data associated with the invoice document being processed.
The LBBIL_INVOICE-HD_REF structure contains information on the various reference documents of the invoice – delivery, sales doc, etc. However, there were a couple of fields in the structure that I was not sure of their usage: VBELN_VAG, VBELN_VKT, and VBELN_VG2 . So, I did a little research, and am documenting my findings here. Continue reading ‘LBBIL_INVOICE Reference Document fields’
•October 24, 2012 • Leave a Comment
We have a custom program that calls the function module CP_BD_DIRECT_INPUT_PLAN_EXT to assign object dependencies to routing operations. Recently, this program failed with the error ”No authorization to edit the alternative” (C\ 017).
I discovered that this error is raised by the function module CP_DI_IMPORT_KNOWLEDGE. It compares the change master being used for the object dependency assignment to the change master on the operation to which the dependency is being assigned. If a different change master is being used for the OD assignment, but it has the same effective date as the change master on the operation, then this error is raised.
•April 19, 2012 • Leave a Comment
Today I had some logic in a user exit that worked fine when executed interactively, but failed when it ran in the background. Upon debugging, I found that the failure was due to an auth check. The user ID was the same, so why would a user have authorization in foreground but not in background?
Continue reading ‘Auth check failing in background’
•January 13, 2012 • Leave a Comment
The first time you open up transaction SWNCONFIG all those options can be very confusing. There’s several tutorials out there that give you step-by-step instructions, but still leave you unclear on what you’ve actually done. Here’s a high-level diagram I put together to help illustrate the relationships between the different configuration sections.
Continue reading ‘SAP Workflow Extended Notification Configuration’
•July 6, 2011 • 1 Comment
When configuring SAP Workflow Extended Notifications in transaction SWNCONFIG you have to specify run schedules for both the selection of work item notifications (“Schedule Selection”) and the delivery of notifications (“Delivery Schedule”). Each schedule has a start time, end time, and interval.
The start time is required while the end time is optional. So, what happens when you specify a start time without an end time?
You might assume as I did that the schedule will run at the specified interval from the start time to the end of the day. In actuality though, SAP ignores the interval and runs the schedule once at the start time. If you want the interval taken into account you must specify both the start and end time.
•June 1, 2011 • 4 Comments
We have a program that uses the function module PRELIMINARY_POSTING_FB01 to park journal entry documents. We recently encountered the error “Enter rate GBP / USD rate type M for 00/00/0000 in the system settings” (SG105) coming back from this function module.
Continue reading ‘Error SG105 parking document with currency conversion’
•May 2, 2011 • 1 Comment
We’re changing the way we process workflow email notifications in SAP, moving from the old RSWUWFML2 method to the newer Extended Notification method. While testing the Extended Notification by running the program SWN_SELSEN I noticed that each run generated 86 entries in the application log:
Looking closer, I saw that most of these entries were basically debugging messages: Entering and Leaving messages for each method that was called. I don’t need that level of logging in production, so can I reduce it without turning off logging altogether?
Eventually I found that there is a parameter to control the level of logging. It is maintained in transaction SWNCONFIG under General Settings. The parameter name is MAX_PROBCLASS and you can set it to a value between 1 (Very Important) and 4 (Additional Information). If no value is specified a default value of 4 is used.
You can see some additional information on this parameter by looking at the documentation for the data element BALPROBCL in SE11.