Back in July, I suspended my series on the SAP B1 Web client due to some frustrating deficiencies in the production module. SP2508 was supposed to fix some of these. Unfortunately, SAP fixed none of them. Instead of suspending this for another few months until more bugs are fixed, I’m going to review those issues and use this as an opportunity to explore something I usually do in the LucaERP newsletter: describe why companies and developers make decisions when building an ERP.

I’m building an ERP system from scratch to explain all the issues involved in developing an ERP. We’ve looked at user interfaces and have been working on content for a few newsletters. It’s time to assemble everything and make the hybrid template we’ll use the most in LucaERP modules. As I’m mostly an Apple developer, I use SwiftData for persistence. If you want to know more about SwiftData, check out my course, …

In SAP, we use two columns regularly: DocNum and DocEntry. But do you know what they actually mean, where they come from, and why you would want to use one over the other? What do they have to do with the ValidFor column? Let’s deep dive into DocNum and DocEntry to explore their many uses and strategies for use.

I’ve been writing an ERP from scratch for a few months and have gotten some of the foundations down before we get into coding modules. The three templates for interacting with data are most important: a form, a report, and a hybrid. The hybrid template became a form that could optionally contain a report, and that’s what I will be using moving forward for all three.

We're building an ERP from scratch and are currently working on three templates to do all the work. We've completed the form and the reporting view. Invoices, bills of materials, and other modules require a template that has three components: a form at the top called a *header*, a report in the middle known as the *body*, which contains details, and a form at the bottom called a *footer*. This time, we'll combine the two templates we have to create the third. Before we do, there's one improvement we'll make to the report: Adding predicates.

I’m building an ERP system from scratch to explain all the issues involved in making an ERP. Unfortunately, I’m late again on an installment of Luca ERP due to a bug in the code I was supposed to write. The bug is due to a Swift UI feature: my improper use of ForEach. As an aside to my usual work, I wanted to write about it in case anyone else gets confused by it.

Heres a .png version of the Apple Icon template for those of you withouth sketch or Adobe Illustrator. Drop it in as a layer in ahtever applcation you use. Download

For those not following the tech news, the nightmare that is Microsoft Recall is back. If not careful, Recall can become a huge security risk for SAP Business One Users. In Spring 2024, Microsoft introduced a feature coming later that year to Microsoft Windows 11: Recall. Recall is effectively a personal search engine of the user's activity run by AI.

It's April Fool's Day, so something silly is called for. What about a parody of a Monty Python Parody about SAP Business One users? What about an absurd story about a missing feature in SAP B1 and the adventure of implementing it? Only Monty Python and the Holy Grail makes sense to tell it, although the story is all too common.

*Note:As I've gained a few followers and subscriptions in the last few weeks, I want to remind everyone that I alternate between LucaP and BizOneness weekly. In LucaP, we're building an ERP system starting at the core: the General Ledger. This week, we'll tie together what we've done by building the General journal. I'm going to change the terms I've used so far.

While I had planned something about the General Ledger for this newsletter, circumstances changed, so I'll do something entirely different. As many of you know, I'm no longer with Scientific Device Laboratory. If you'd like to know more about that situation, I have described it in detail here, but the very short version is that I lost the ability to access SAP B1 for this newsletter for the last nine months.

#Bizoneness While I had planned something about the General Ledger for this newsletter, circumstances changed, so I'll do something entirely different. As many of you know, I'm no longer with Scientif...

Thoughts and Tips for participating in the Swift Student Challenge

In the ERP application, we have established credits and debits on a ledger with the five major accounts. However, we don't know what those credits and debits do. We want the ledger to tell the story of how we moved our money around. That's where the chart of Accounts comes in. In the ERP application, we have established credits and debits on a ledger with the five major accounts.

How do you start to understand the workings of an ERP system? By making one. In this biweekly column, we’ll make an ERP system and start at the core of it all: accounting. This lesson will be longer than subsequent lessons, as I will have to do some background and definitions so everyone has an equal idea of what is going on.

#Bizoneness Data migration is taking data from one source and merging it into another source. If you're very lucky, it will be a seamless change.

SOme people have sales, I give things away for a limited time. Check out my Swift Data course on LinkedIn Learning! I have made it free for you with the link…