Toolkit for SAP consultants

How to add a new field to MB51?

noreply@blogger.com (Dzmitryi Kharlanau) — Thu, 06 Jun 2024 09:47:00 +0000

If the field is from MKPF or MSEG, then just fill checkboxes in

SPRO >> IMG>>Materials Management>>Inventory Management and Physical Inventory>>Reporting>>Define Field Selection for Material Document List

If it is not, then

Open the program RM07DOCS

1) Extend the structure

Before DATA: END OF list. add the enhancement with your field.

2) Add the logic to fill in the beginning of FORM output_list.

3) Add the field to the field catalog in the end of, as for example:

INSERT VALUE #( fieldname = 'MATKL'

tabname = 'LIST' ref_tabname = 'MARA'

ref_fieldname = 'MATKL' )

INTO TABLE fc_flat.

Why should you have a personal blog if you are an SAP Consultant?

noreply@blogger.com (Dzmitryi Kharlanau) — Mon, 13 Nov 2023 07:56:00 +0000

Having a blog as an SAP consultant offers several significant benefits, particularly in terms of building a knowledge base, recording ideas, and promoting transparency. Here's a breakdown of why it's a good idea:

Building a Knowledge Board:
- Sharing Expertise: A blog allows you to share your expertise and insights on SAP products and the industry. This helps in building a repository of knowledge that can be beneficial both for you and for others in the field.
- Continuous Learning: Writing about different aspects of SAP forces you to stay updated with the latest trends and technologies. This continuous learning not only enriches your blog but also enhances your professional skills.
Recording Ideas:
- Idea Incubation: Blogs can serve as a platform to brainstorm and nurture ideas. Writing about theoretical concepts or potential solutions to common problems can lead to innovative approaches in your work.
- Feedback Loop: By sharing your ideas publicly, you invite feedback from peers, which can help refine your thoughts and strategies. This interactive process can lead to more robust and well-thought-out solutions.
Promoting Transparency:
- Building Trust: Sharing your successes, challenges, and learning experiences on a public platform can build trust with clients and peers. It shows that you are open about your professional journey and willing to learn from experiences.
- Networking and Reputation: A well-maintained blog can enhance your reputation as a knowledgeable and approachable professional. It can also help in networking, as it attracts readers from different areas of the SAP ecosystem.
Professional Development:
- Showcasing Skills: Your blog can act as a portfolio of your skills, problem-solving capabilities, and your understanding of complex SAP solutions.
- Career Advancement: A successful blog can open doors for professional opportunities, such as speaking engagements, consultations, or even new job offers.
Community Engagement:
- Building a Community: By sharing your knowledge and experiences, you can build a community of like-minded professionals. This community can be a source of support, collaboration, and new ideas.
- Mentorship Opportunities: As your blog grows, it can become a platform for mentoring others entering the field, thereby giving back to the SAP community.

In summary, a blog can be an invaluable tool for an SAP consultant. It's not just about sharing knowledge; it's about creating a dynamic space for growth, learning, and professional development.

Should We Rush Inconsisteny fixes When Risk is Low?

noreply@blogger.com (Dzmitryi Kharlanau) — Mon, 13 Nov 2023 07:54:00 +0000

Let's chat about something we often run into in the SAP world: quick fixes. You know how it is – customers usually want things done yesterday, right? But is speeding through a solution always the best path?

Let's think about it. When a customer comes to us with a problem, and we know there's a fast solution that carries a tiny risk (like less than 10%), it's tempting to just go for it. Especially if we're not messing with anything in financials (FI), which can be super tricky.

But here's the deal: even if the risk is low, we've got to weigh our options. Quick fixes can be great, but they're not always the long-term answer. What if it's just a Band-Aid on a bigger issue? Sometimes, taking a bit more time to really dig into the problem can save a lot of headaches later.

So, my philosophy? If it's low risk and not in the financial zone, sure, consider the fast track

The Magic of Quick Fixes

Think about it: when you swoop in and quickly untangle a complex problem, you're not just fixing an issue. You're delivering peace of mind. You're showing your client that they can trust you to handle the unexpected with agility and expertise. This is huge in building long-term relationships.

Reputation Building

Every time we deliver a quick fix, we're also sending out a message: we're efficient, we're capable, and we're reliable. This is the kind of reputation that spreads. In a world where word-of-mouth and peer recommendations are gold, being known as the consultant who delivers fast can open new doors and bring in more exciting opportunities.

But, There's a Catch

While quick fixes are great, it's important to strike a balance. We should never compromise on quality for speed. It's all about finding that sweet spot where efficiency meets excellence. And when we do find it, it's worth talking about.

But always, always think about the bigger picture. What's your take on this? Have you had experiences where a quick SAP solution was the way to go? Or times when it backfired?

How to Copy Contract Text to PO Item Text Effectively?

noreply@blogger.com (Dzmitryi Kharlanau) — Tue, 07 Nov 2023 08:21:00 +0000

As an SAP MM consultant, one of the essential tasks is to ensure the smooth transition of information from contracts to purchase orders (POs). A common requirement that arises is the need to copy text from contracts into the item text of POs. This functionality is crucial for maintaining consistency and ensuring that all the terms agreed upon in the contract are accurately reflected in the purchase orders. But how can this be done efficiently within SAP?

The solution lies in setting up the appropriate copying rules for item texts within the SAP customizing path. Let's delve into the step-by-step process that allows for a seamless transfer of text from contracts to POs.

Step 1: Navigate to the Customizing Path First, you will need to access the SAP customizing path. You can do this by following the navigation below:

SPRO → SAP Reference IMG → Materials Management → Purchasing → Purchase Order → Texts for Purchase Orders → Define Copying Rules for Item Texts in Purchase Orders

This path will lead you to the configurations where you can define the rules for how texts are copied from one document to another.

Step 2: Define Copying Rules Once you're in the correct menu, you're faced with defining the copying rules. These rules dictate how the system will handle the text during the creation of a PO from a contract.

In the ‘Define Copying Rules for Item Texts in Purchase Orders’ section, you will specify the source text object (in this case, the contract) and the destination text object (the PO item text).

Step 3: Set Up the Sequence It’s not just about defining the rules; it’s also crucial to set up the sequence in which the system checks for texts to copy. This sequence determines the priority of texts when there are multiple texts available to copy from. You have to make sure that the contract text has a higher priority so that it gets copied over other texts.

Step 4: Test the Configuration After setting up the rules and sequence, it is essential to test the configuration to ensure that texts are being copied as desired. Create a contract with text, then create a PO referencing this contract and check if the item text is copied correctly.

Conclusion: Setting up the copying rules for item texts in POs is a straightforward process but requires attention to detail to ensure that the information flows correctly. For SAP MM consultants, mastering this process can lead to more efficient data handling, fewer errors, and a clear alignment between contracts and purchase orders. As always, after any customization, thorough testing is key to a smooth operation. Keep this guide at hand for when you need to ensure your contract texts make it to your PO items without a hitch.

SAP Solutions: Balancing the Budget with Custom Smarts

noreply@blogger.com (Dzmitryi Kharlanau) — Mon, 06 Nov 2023 09:57:00 +0000

You've probably heard the saying, "You get what you pay for," right? Well, in the world of big business software, SAP solutions are kind of like the fancy sports cars of the road. They're packed with features, they go super-fast when it comes to crunching numbers, and they look good on the company’s 'driveway'. But yep, you guessed it - they can come with a hefty price tag. So, let’s chat about why SAP can make your wallet feel a bit lighter and how a SAP consultant, like a smart car mechanic, tries to tune it just right to balance those costs.

The High Price of Being Top Notch

SAP is like a toolbox that's bursting with every tool you could imagine. It’s got hammers, screwdrivers, and gadgets that some folks might not even recognize! For a business, that's awesome because it means SAP can handle just about anything they throw at it - from keeping track of money to making sure products are shipped on time.

But here’s the deal - all those tools and features? They don’t come cheap. It's like paying extra for a phone with a super camera and a zillion other features you might not even use. And because SAP is top-of-the-line, it requires some serious experts to run it, which can add to the cost.

The Role of a SAP Consultant

Enter the SAP consultant - think of them as the mastermind mechanics who know how to tune that sports car perfectly. They look at what a company needs and then figure out how to make SAP fit those needs without buying all the bells and whistles that'll cost an arm and a leg.

Custom Developments: The Cost-Saving Trick

One way to avoid spending too much is by using custom developments. That’s when the consultant rolls up their sleeves and creates special code or modules just for what the company really needs. It's like getting a custom part for your car instead of buying a whole new engine when all you need is a bit more vroom.

Finding the Balance

But here’s the kicker - custom stuff can also get pricey if you go overboard. It’s all about balance. A good SAP consultant will know just how much custom work to do to make the SAP system do its magic without creating a monster that’s expensive to maintain or too complex to handle.

Long-Term Thinking

The consultant has to think long-term, too. Sure, custom development might save some cash now, but what about later? They have to make sure whatever they do won't cost a fortune to change or update down the line. It's like making sure the custom part in your car isn't going to be super rare and costly when it's time for repairs.

Wrapping It Up

SAP might seem like it costs a pot of gold, and honestly, it can. But with a savvy SAP consultant working their magic, companies can have their cake and eat it too. It’s about using those custom developments cleverly, being smart about what's really necessary, and always thinking about how today’s decisions will play out on tomorrow’s business highway.

So yeah, SAP solutions come with a fancy price, but with the right consultant, you’re not just throwing money at a problem. You’re investing in a tailored fit - something that runs like a dream and gets you where you need to go without buying the whole car dealership.

Why Do Companies Pick SAP Solutions? It's Simpler Than You Think!

noreply@blogger.com (Dzmitryi Kharlanau) — Mon, 06 Nov 2023 09:56:00 +0000

When you stroll through the aisles of a big supermarket, have you ever wondered how they manage to keep track of so many different items? Or how does a car manufacturer know they have all the right parts to build thousands of cars? Well, a good chunk of them have a secret sauce helping them manage all this: SAP solutions.

What’s SAP Anyway?

SAP stands for "Systems, Applications, and Products in Data Processing." It’s like a giant, sophisticated computer brain that helps businesses of all sizes – from your local bakery to international airlines – juggle their daily tasks more efficiently. But why do so many companies love SAP? Let's break it down.

1. Everything in One Place

Imagine having all your work tools scattered in different rooms. Every time you need a stapler or a calculator, you have to run from one room to another. Pretty tiring, right? SAP brings all the tools a company needs into one 'digital room'. It ties together accounting, sales, production, human resources, and more - all in one system. This means less running around and more time being productive.

2. Speaking the Same Language

Every department in a company is like a person in a large family. If everyone speaks their own language, things can get confusing. SAP is like a universal translator that helps everyone understand each other. This means when the sales team sells something, the warehouse team immediately knows to pack it up, and the accounting team knows to invoice it. Neat, isn't it?

3. Learning from the Past

SAP is also a bit like a wise old owl. It doesn’t just record what's happening now; it remembers what happened before. This memory helps companies make better decisions. If a particular product sold really well last year, the company might want to stock up on it. SAP helps them remember these golden nuggets of information.

4. Planning for the Future

Companies also use SAP for something called "ERP" - that's short for Enterprise Resource Planning. Think of it as planning a big party. You need to know how many guests are coming (sales forecasting), how much food to buy (inventory), and how many tables you need (production). SAP helps companies plan all these details so that when the big day comes, everything runs smoothly.

5. Adapting to Change

Let's face it, the world changes a lot. New laws, new trends, new technologies. SAP helps companies stay flexible. When a new law comes out, or a company wants to start selling a new product, SAP has tools to help them adapt without turning their world upside down.

6. Big Decisions Made Easier

Imagine trying to choose what to watch on TV without a remote control. SAP is like a remote for CEOs and managers. It gives them a clear screen where they can see everything that's happening in their company, making it easier to press the 'right buttons' and make big decisions.

7. Safety First

SAP also acts like a safe where companies keep their valuable information. It has lots of locks and security measures to make sure that only the right people can see the company's sensitive data. This way, they can protect their secrets from competitors.

8. Global Friendliness

In today's world, companies often work across different countries. SAP is like a global citizen; it can handle different currencies, languages, and laws. This makes it a great fit for companies that have teams around the world.

Wrapping Up

In simple terms, companies choose SAP because it makes their lives easier. It's an all-in-one system that speaks everyone's language, remembers important stuff, helps plan for the future, adapts to changes, helps make big decisions, keeps things safe, and is friendly all over the world. That’s why SAP is like a super-helper for businesses - big or small. Just like a Swiss Army knife, it's packed with tools that can tackle almost any job in the corporate world!

TM: Freight Order Management

noreply@blogger.com (Dzmitryi Kharlanau) — Fri, 25 Feb 2022 13:53:00 +0000

You can use the business documents in freight order management to enter all the information required for transportation planning and execution, such as source and destination locations, dates/times, product information, and resources used.

You can create freight orders directly or in transportation planning. For example, you can assign freight units to the freight orders and have the system calculate the transportation charges.

Freight order

Order for which execution is planned by a carrier or the shipper. Use freight orders primarily for land transportation (road freight order) and rail transportation.

Transportation Management under Freight Order Management Freight Order Define Freight Order Types.

Content

Planning information
Business partner
Driver
Locations and dates/times
Items

Quantities and weights (see Quantities and Capacities)
Goods information (see Goods Information)
Corresponding freight orders (see Pick-up and Delivery Freight Orders)
Dangerous goods information (see Considering Dangerous Goods)
Seal information (see Use of Seals)
Information about foreign trade (see Integration with SAP Global Trade Services)
House bill of lading (see Building of House Bills of Lading and House Air Waybills)
Service items
Cargo items
Execution information, for example, actual departure times
Transportation charges
Status information and blocking information
Customs-relevant information
Output management

Customizing

Integration settings

Define freight order types and assign valid item types and event codes to them.

Order type determination

The system determines freight order types in one of the following ways:

If you create freight orders during planning and have configured the respective settings in the planning profile (Business Document Type area), the system determines the freight order type according to your settings.
If you create freight orders from your forwarding order stages, the system uses the freight order type that you have defined in the Customizing activity Define Default Capacity Document Types for Stages.
If freight units are converted into freight orders when direct shipment options (DSO) are determined, the system uses the freight order type that you specified for DSO in the freight unit type.
The system uses the default freight order type that you define in this Customizing activity.

Production planning in Process industry

noreply@blogger.com (Dzmitryi Kharlanau) — Wed, 23 Feb 2022 15:58:00 +0000

Grundsätzlich ist die Prozessfertigung chargenorientiert, d. h., für die hergestellten Mengen erfolgt spätestens bei der Zugangsbuchung in das Lager die Vergabe einer Chargennummer.

Grundlage für die Struktur und den Funktionsumfang der Komponente PP-PI ist die Norm ANSI/ISA-88 für die chargenorientierte Fahrweise (Batch Control).

Entscheidend hierfür ist, ob Sie im Materialstamm ein PP- oder PP-PI-Fertigungssteuerungsprofil zugeordnet haben und ob in der Fertigungsversion ein Arbeitsplan der Komponente PP oder ein Planungsrezept der Komponente PP-PI zugeordnet wurde.

Stammdaten

Das Planungsrezept ist das Hauptelement der PP-PI-Stammdaten, dem alle anderen in gezeigten Elemente zugeordnet werden, mit Ausnahme der Charge.
Materialien werden auf Kopfebene und als Komponenten in der Materialstückliste zugeordnet. Ressourcen werden im Vorgang zugeordnet und beschreiben den Ort, an dem der Produktionsschritt ausgeführt wird.
Die Fertigungsversion verbindet das Planungsrezept mit der Stückliste und stellt eine Fertigungsalternative dar.
Mit XSteps, die als Referenz zugeordnet oder direkt angelegt werden, beschreiben Sie die konkreten Ausführungen der Produktion.

Materialen

Disposition 2: Chargenerfassung ( für Komponenten der Stückliste ) ... when batches have to be determined

Charge beim Warenausgang, keine Rückmeldung erforderlich
Manuelle Chargenfindung bei Auftragsfreigabe erforderlich
Charge nicht im Fert.-/Prozeßauftrag erforderlich, Rückmeldung erforderlich
Automatische Chargenfindung bei Auftragsfreigabe

Disposition 2: Produktionslagerort

If the material is a component, it is the issuing storage location to which a backflush is posted.
If the material is produced, it is the receiving storage location to which the receipt of the material is posted.

Disposition 2: Retrogr. Entnahme ( nur für Komponenten relevant )

Disposition 2: Kuppelprodukt ( Material can be co-product )

Disposition 2: Terminierung ( Scheduling )

Disposition 3: Verfügbarkeitsprüfung

Disposition 4: KompAusschuß (%)

Percentage of scrap that occurs during production of the material if the material is a component.

Arbeitsvorbereitung: Fertigungs-ME

Arbeitsvorbereitung: Fertigungssteuerer & FertigungsstProfil

specify that certain business transactions are carried out in parallel in a production order / process order (you can, for example, create and release an order at the same time, or release an order and print the shop papers)
trigger an automatic goods receipt
specify an overall profile for capacity leveling

Arbeitsvorbereitung: Toleranzdaten

Ressourcen

Arbeitsplatz: Produktionsplanung Prozeßindustrie • Stammdaten • Ressource • Allgemeine Daten • Ressourcenart (Arbeitsplatzart) einstellen (Transaktion OP40 Work center category ).

Work Center Category/ Field selection / Screen sequence / Status Profile

Eine Ressource legen über den Menüpfad Logistik • Produktion Prozeß • Stamm daten • Ressourcen • Ressource • Anlegen (Transaktion CRC1) an.

Verantwortlicher, für die Planverwendung wählen Sie im Regelfall die Einstellung 008 für die Kombination aus Planungsrezept und Prozessauftrag aus,...
Vorschlagswerte
Kapazitäten
Terminierung
Kalkulation

Das Ressourcennetz verwenden Sie für die Festlegung von möglichen Ressourcenreihenfolgen im Produktionsprozess. Ein Ressourcennetz legen Sie über den Menüpfad Logistik • Produktion Prozeß • Stammdaten • Ressourcen • Ressourcennetz • Anlegen (Transaktion CR24) an. Ressourcennetze werden häufig verwendet, wenn gleichartige Ressourcen zur Verfü gung stehen und die Auswahl der konkreten Ressource erst kurz vor Beginn der Pro duktion erfolgen soll.

Voraussetzung für die Verwendung der Ressourcenauswahl im Prozessauftrag ist die Zuordnung eines Ressourcennetzes im Kopf des Planungsrezepts.

Stammdaten der Ressourcenauswahl mit Klassifikation ( Class 019 ), then assign to Resource.
Die Anlage der Selektionskriterien erfolgt im Planungsrezept über den Menüpfad Logistik • Produktion Prozeß • Stammdaten • Planungsrezept • Rezept und Material liste • Ändern (Transaktion C202).

Integrierte Stammdatenpflege über Fertigungsversionen

Mithilfe von Fertigungsversionen legen Sie mögliche Kombinationen von Planungsrezepten und Stücklisten fest, mit denen ein Material produziert werden kann.

Create production version in material master at the View: Disposition 4 or Arbeitsvorbereitung.

Zur Pflege eines Planungsrezepts verwenden Sie den Menüpfad Logistik • Produktion Prozeß • Stammdaten • Planungsrezepte • Rezept und Materialliste • Ändern (Transaktion C202).

Logistik • Produktion Prozeß • Stammdaten • Ferti gungsversionen (Transaktion C223).

Planungsrezepten

Planungsrezepte beschreiben den Ablauf eines Produktionsprozesses der Kompo nente PP-PI und beinhalten alle notwendigen Vorgaben wie z. B. Produktionsmittel (Ressourcen) und Komponenten zur Herstellung von Produkten.

Ein Planungsrezept besteht aus einem Kopf und mehreren Vorgängen, die auf einer Ressource (Primärressource) ausgeführt werden.

Ein Vorgang fasst eine bis n Phasen zusammen. Die Phase beschreibt detailliert einen Teil des gesamten Herstellungsprozesses und enthält die notwendigen Informationen, um Termine, Kapazitätsbedarfe und Kosten ermitteln zu können

Zusätzlich zu den Primärressourcen können den Vorgängen und Phasen Sekundär ressourcen zugeordnet werden, die während der Abarbeitung eines Vorgangs bzw. einer Phase benötigt werden, wie z. B. Behälter oder Drucker

Den Vorgängen und Phasen können jeweils mehrere Prüfmerkmale für fertigungs begleitende Prüfungen zugeordnet werden

Für die Prozesssteuerung können im Planungsrezeptkopf XSteps (Execution Steps) angelegt und referenziert werden. Alternativ können Sie einer Phase auch Prozessvorgaben zuordnen.

Rezeptkopf: Status, Verwendung, Qualitätsprüfungen, Vorgänge und Phasen

TM: Internal Settlement Management

noreply@blogger.com (Dzmitryi Kharlanau) — Wed, 23 Feb 2022 09:11:00 +0000

Create an internal settlement document for a transportation service provided to you by an internal organization in your company. The internal organization bills you to recover the cost of the transportation services it provided to you when you fulfilled a forwarding order to a customer

TM: Freight Settlement

noreply@blogger.com (Dzmitryi Kharlanau) — Wed, 23 Feb 2022 09:10:00 +0000

Use
Freight Settlement Document
Customizing
Process

New FSD
Add or change charge amounts directly in the existing freight order
Change charge amounts directly in the freight settlement document
Reversing a Freight Settlement Document
Follow-Up Freight Settlement Document

Use this component to trigger the verification of an invoice, received from a supplier or carrier for transportation charges.

Create a freight settlement document in SAP TM for the transportation services provided to you by a carrier. SAP TM transfers the freight settlement document to SAP ERP. You can verify the invoices you receive from your carrier against the information contained in the freight settlement document.

The transportation charges are calculated in SAP Transportation Management (SAP TM) on the basis of a freight order, service order, or freight booking.

Freight Settlement Document

You can create an individual FSD for one freight order, service order, or freight booking. You can create a collective FSD for multiple freight orders or freight bookings. You can also create multiple FSDs at the same time.

FSD document

General Data
Business Partner
Charges: Customizing for Transportation Management under Basic Functions Charge Calculation Basic Settings Define Calculation Profiles
Orders
Document Flow

Status

Ready for Accruals (.. is ready for you to transfer to accruals in SAP ERP )
Transferred for Accruals
Accruals Posted ( ERP system successfully created the PO and SES )
Invoice Verified in SAP ERP
Cancellation Requested in SAP ERP
Canceled
Reversal Requested in SAP ERP
Reversal Requested in SAP ERP ( It automatically enabled the returns indicator in the SES )
Credit Memo Created in SAP ERP ( SAP ERP system posted a credit memo against the reversed FSD to reverse the accruals posting )

Process

New FSD

Create the freight settlement document (... Mass Creation of Freight Settlement Documents )

System uses certain criteria to divide settlements when you choose to create a collective settlement document

Review the settlement document details for consistency
Transfer the settlement document to SAP ERP to post accruals
SAP ERP confirms the accrual creation
SAP ERP verifies the expected invoice against the actual invoice

Add or change charge amounts directly in the existing freight order

Use the background function Creation and Transfer of Freight Settlement Documents (program /SCMTMS/SFIR_CREATE_BATCH) to create, change, and transfer freight settlement documents to SAP ERP

If the new or changed amount results in the invoicing status of the freight order changing to Partially Invoiced, you can create a new freight settlement document to send the changed amounts to SAP ERP.
If the new or changed amount results in the invoicing status of the freight order changing to Over Invoiced, you can create a credit memo in SAP TM to send the changed amounts to SAP ERP.
If you do not want to create a new settlement document or credit memo, you can cancel the existing settlement document provided the life cycle status of the settlement document is not Invoice Verified in SAP ERP. You can then create a new settlement document that contains the complete amount including the changes.

Change charge amounts directly in the freight settlement document

..., provided the life cycle status of the settlement document is not Invoice Verified in SAP ERP. When you transfer the settlement document to SAP ERP, SAP ERP cancels the existing purchase order and SES and creates a new purchase order and SES.

Reversing a Freight Settlement Document

Follow-Up Freight Settlement Document

Customizing

Transportation Management under Settlement Freight Settlement
Transportation Management under Settlement Define Settlement Profile
Transportation Management under Basic Functions Charge Calculation Basic Settings Define Calculation Profiles
Transportation Management under Settlement Configure Process Controller for Settlement
Transportation Management under Master Data Business Partners Define Partner Determination Profiles
SAP ERP Central Component Logistics Materials Management (MM) External Services Management (MM-SRV) Master Records from the ESM View Service Master Record

Invoice integration

Logistics Invoice Verification (MM-IV)

The user parameter TM_INVOICE_CLERK.
Activate the workflow WS53800006 for the incoming invoice (BUS2081) so that the connected transportation management system is informed by a service. In addition, you must activate event linkage for the events POSTED and CANCELLED.

BAPI List

BAPI_INCOMINGINVOICE_CREATE1: Invoice Verification: Hold/ Park/ Park As Complete/ Post Incoming Invoice
BAPI_INCOMINGINVOICE_GETDETAIL: Invoice Verification: Display Incoming Invoice
BAPI_INCOMINGINVOICE_GETLIST: Invoice Verification: List Incoming Invoices
BAPI_INCOMINGINVOICE_CHANGE: Invoice Verification: Change Provisional Invoice
BAPI_INCOMINGINVOICE_DELETE
BAPI_INCOMINGINVOICE_POST
BAPI_INCOMINGINVOICE_CANCEL

TM: Forwarding Settlement

noreply@blogger.com (Dzmitryi Kharlanau) — Wed, 23 Feb 2022 09:10:00 +0000

Create a forwarding settlement document in SAP TM to bill a customer for the transportation services you provide to the customer. SAP TM transfers the forwarding settlement document to SAP ERP and SAP ERP sends the invoice to the customer.

Quality Planning

noreply@blogger.com (Dzmitryi Kharlanau) — Tue, 22 Feb 2022 13:34:00 +0000

Creating and Changing QM Data for a Material

Inspection Setup

Creating and Changing QM Data for a Material

Unit of issue: Define the unit of measure that can be used for the withdrawal of a material from the warehouse, stock transfers and transfer postings.
QM material auth. use this key to limit the access authorization of users to the material-related data in Quality Management.
GR processing time enter the number of working days that are needed to inspect the material and place it in storage, once the goods have been received. This field is for information only.
Catalog profile Assign a catalog profile to the material. This profile is then proposed as the default when you create a quality notification or record defects.
Inspection setup
Post to insp. stock indicator If you set this indicator, the material is posted to inspection stock at goods receipt.

This field is hidden if at least one inspection type relevant to stock is active.

Documentation reqd You set this indicator, if you want to record any changes made to inspection lots that were created for the material in change documents.
Inspection interval In this field you enter the period of time in days until the next recurring inspection is to take place. This field only applies to materials that are to be handled in batches.
QM procurement active If you set this indicator, you activate Quality Management in procurement for all plants in a client.
QM control key Use this key to control the conditions that apply to the quality management processes in procurement.

Certificate type Enter a certificate type if you have selected a control key that requires a certificate type.
Tech. delivery terms This indicator is set automatically, if technical delivery terms are assigned to a material. You must assign technical delivery terms to a material, by choosing the corresponding control key.

Inspection Setup

Inspection lots are created for all goods movements that are relevant to QM. In the material master, you define which goods movements are relevant to QM.

Insp. with mat. spec indicator: The inspection is carried out according to the material specification.
Insp. with task list indicator: The inspection is carried out according to the material specification.
Insp. by configuration indicator: When inspection lots are created, the system takes into account the variant configuration from the sales order or production order. The inspection specifications from the task list or the material specification are supplemented or changed.
Inspect by batch indicator: When inspection lots are created, the system takes into account the specifications that have been defined in batch determination.
Automatic assignment indicator: The system assigns an inspection plan or a material specification automatically, so that the inspection lot can be made available without any further processing
Insp. by charac. indicator: Results recording based on characteristics takes place. This is a prerequisite for dynamic modification based on characteristics. You can only set this indicator in conjunction with the Insp. with task list or Insp. with mat. spec. indicator.
Smpl. procedure: Sampling procedure, according to which the sample size is to be calculated from the lot quantity. In addition, the sampling procedure defines the type of valuation that is used to record results. This field is only relevant for an inspection without a task list or material specification.
100% inspection indicator: An inspection of the whole inspection lot takes place.
Inspection % field: Percentage, according to which the total sample size is to be calculated from the lot quantity. This field is only relevant for an inspection without a task list or material specification.
Manual sample calc. indicator: trigger the sample calculation in the inspection lot manually.
Manual sample entry indicator: Enter the sample size in the inspection lot.
Dyn. mod. rule indicator: The dynamic modification rule defines inspection stages and the conditions that lead to an inspection stage change.
Skips allowed indicator: The system allows characteristics to be skipped when the sample size is calculated. If you do not set this indicator, at dynamic modification, the system chooses the next inspection stage that is not a skip.
Automatic UD indicator: The system can automatically make usage decisions for inspection lots when the corresponding program is run.
Single-unit insp. indicator: A single-unit inspection using serial numbers is activated for the inspection lot, provided that the material has been identified by a serial number profile as requiring serial numbers.
Avg. insp. duration field: You enter the average inspection duration in days. The start or end date for the inspection is then calculated at inspection lot creation using the start or end date and the inspection duration.
Q-score procedure: Quality score procedure, according to which the quality score is calculated.
Allowed scrap share field: Allowable share of scrap for the quality score procedures that use the share of scrap to calculate the quality score.
Control Ins Lot: enter the conditions under which a single inspection lot is to be created.
QM individual order indicator: You can record appraisal costs for the combination material/inspection type in an individual QM order.

QM order: Number of the QM order, in which the costs are to be collected.

Transactions:

QA08 Making Mass Changes to the Inspection Setup

ABAP Development for SAP TM

noreply@blogger.com (Dzmitryi Kharlanau) — Mon, 24 Jan 2022 08:17:00 +0000

LE-TRA

User Exits for SD Transport Processing
Statusermittlung bei Aufruf aus der Lieferungsbearbeitung

Integration

Sales Order Integration with External
Delivery Integration with External TMS
Purchasing Document Integration with External TMS
BAdI: Location Creation for Business Partners
Selection of Outbound Interfaces Processed for Purchase Order

LE-TRA

LV45P025/transportstatus_lieferung

* Check if TM controls the planning status

SELECT SINGLE pln_status_upd_tm_ind int_mode FROM tms_c_control
INTO CORRESPONDING FIELDS OF ls_tms_ctrl WHERE tm_ctrl_key = f_likp-tm_ctrl_key.

User Exits for SD Transport Processing

EXIT_SAPLV56U_007: Additional Rules for Determining Transportation Planning Status

The transportation planning status of the affected deliveries is updated if a shipment is saved during shipment processing. You can determine the transportation planning status of deliveries with additional rules in this function.

Integration

Purchasing Document Integration with External TMS

Delivery Integration with External TMS

CHANGE_TM_CTRL_KEY: You can use this BAdI method to change the control key assigned to the delivery types.

CHANGE_LOG_TM_NR: You can use this BAdI method to change the technical transportation management number assigned to the delivery types.

Sales Order Integration with External TMS BADI_LO_TM_SLS BAdI

CHANGE_TM_CTRL_KEY: You can use this BAdI method to change the control key assigned to the sales document types.

Specifies which documents in a document chain are to be integrated into TM.

CHANGE_LOG_TM_NR: You can use this BAdI method to change the technical transportation management number assigned to the sales document types.

BAdI: Location Creation for Business Partners /SAPAPO/LOC_CREATE

BAdI: Adaptation of Location Details, Descriptions and Transportation Zone Assignments /SAPAPO/LOC_DETAILS

Selection of Outbound Interfaces Processed for Purchase Order

PUR_SE_PO_INTERFACE_OUT_SELECT

You have activated the workflow for the asynchronous sending of services for purchase orders. You will find the relevant settings in the SAP Easy Access menu under Tools -> ABAP Workbench -> Development -> SAP Business Workflow -> Definition tools -> Events -> Event creation -> Type Linkage Activated (transaction SWETYPV). You must activate event linkage there for BOR object type BUS2012 (purchase order) and the events CREATED and CHANGED. As standard, this linkage applies to receiver type WS53800008.

PUR_SE_PO_INTERFACE_OUT_SELECT

For purchase orders, transportation relevance in TM is determined by goods movement relevance. In the example implementation, the item category (PSTYP field) is used to decide whether the goods movement relevance indicator is set to 'true' for an item. If it is, the item is given transportation relevance in TM. You can add criteria that are used to determine whether this indicator is set, for example material number, material group, or plant. Note that when querying the item category, you must replace the placeholder with an actual value.

TM Basics

noreply@blogger.com (Dzmitryi Kharlanau) — Wed, 12 Jan 2022 15:46:00 +0000

Organisationsstruktur
Stammdaten
Transportkapazitätsmanagement
Frachtkostenabrechnung

LE-TRA Component (S4/ECC)

Transportation Planning Status

Integration

Customizing
Order integration

Send Sales Order to Transportation Management System / Send Customer Return to Transportation Management System / Send Purchase Order to Transportation Management System
Send Delivery Proposal to SAP ERP (Outbound Delivery)
Send Delivery Proposal to SAP ERP (Inbound Delivery)
Send SAP ERP Delivery to SAP TM
Split Outbound Delivery
Update Outbound Delivery

Invoice integration

Forwarding Settlement ( Customer Freight Invoice Request Processing )
Invoice Simulation
Invoice Notification
Freight Settlement

Posting Goods Issue from TM
Scheduling of SAP ERP Sales Orders in SAP TM

Integration of SAP ERP Scheduling Agreements with SAP TM - SAP Help Portal

TM

Organisationsstruktur

Die Verkaufsorganisation ist in den folgenden Dokumenten relevant: Speditionsangebot, Speditionsauftrag, Speditionsvereinbarung, Speditionsabrechnungsbeleg.

Die folgenden Dokumente sind in der Regel mit der Einkaufsorganisation verknüpft: Frachtauftrag, Frachtbuchung, Serviceauftrag, Frachtvereinbarung, Frachtabrechnungsbeleg.

Planungs- und Ausführungsorganisationen.

Frachteinheit, Packstückeinheit, Transporteinheit, Frachtauftrag, Frachtbuchung, Ressource

Eine Niederlassung ist eine Organisationseinheit, die Verkaufsaktivitäten, Einkaufsaktivitäten sowie Planungs- und Ausführungsaktivitäten durchführen kann und daher jedem der genannten Dokumente und Objekte zugeordnet werden kann.

It is created under Organizational staff and can be read from SAP system.

Stammdaten

Geschäftspartner

Im Spediteurprofil, das für Geschäftspartner mit der Rolle Spediteur in der Transaktion /SCMTMS/TSPP oder auf der klassischen Benutzeroberfläche über den Menüpfad Logistik > Transportation Management > Stammdaten > Transportnetz > Spediteurprofil definieren angelegt werden kann, sind zusätzliche spediteurspezifische Informationen hinterlegt.

Wenn Sie die Organisation eines Unternehmens definieren, werden Geschäftspartner automatisch für die einzelnen Organisationseinheiten angelegt.

Es ist auch möglich, die Mitarbeiter eines Geschäftspartners selbst als Geschäftspartner zu definieren, wenn sie eine eigene Rolle im Unternehmen Ihres Geschäftspartners einnehmen (z. B. den Disponenten oder Ansprechpartner des Spediteurs, der persönlich für Ihr Unternehmen zuständig ist).

Die automatische Zuordnung des Geschäftspartners wird durch ein Partnerfindungsprofil gesteuert, das im Customizing der entsprechenden Belegart zugeordnet werden kann.

Geschäftspartnerfindungsprofil.

Lokation

Die Erstellung von Lokationen auf Basis von Geschäftspartnerstammdaten kann über eine Implementierung des BAdIs /SAPAPO/LOC_CREATE aktiviert werden. Die BAdIImplementierung ermöglicht es, nach dem Anlegen eines Geschäftspartners eine Lo kation anzulegen.
Schließlich können Lokationen auch auf Basis des Reports /SAPAPO/CREATE_LOCATION angelegt werden.

Materialien

Im Materialstamm gibt es eine Vertriebssicht (Vertrieb: allg./Werk), in der Sie die Transportgruppe TranspGr und die Materialfrachtgruppe MatFraGruppe als transportrelevante Attribute pflegen.

Der Umgang mit Gefahrstoffen wird durch zahlreiche Gesetze und Vorschriften geregelt. Wenn ein Material als gefährlich eingestuft ist, müssen Sie einen Gefahrgutstammsatz anlegen, um dieses Material während der Transportabwicklung richtig zu behandeln.

Gefahrgutkennzeichenprofil im Materialstamm

Mit dem DRF werden Stammdaten wie Geschäftspartner, Produkte und Lokationen zwischen Quellsystemen (z. B. SAP ERP oder SAP S/4HANA) und Zielsystemen (SAP TM in SAP S/4HANA) repliziert

Transportnetz

Das Transportnetz definiert die direkte Erreichbarkeit zwischen Ihren Lokationen und Umladelokationen, die gemeinsam definieren, wie Fracht zwischen Ihren Loka tionen transportiert werden kann.

Eine Lokation stellt einen logischen und/oder physischen Ort dar, an dem Waren angeliefert, abgeholt oder umgeladen werden oder an dem LKW und Anhänger gekuppelt oder abgekoppelt werden.

Ein Transportnetz enthält in der Regel eine große Anzahl von Lokationen. Das Transportnetz kann sehr gut über eine Transportzonenhierarchie strukturiert werden, in der Zonen anderen, übergeordneten Zonen zugeordnet werden können.

Transportbeziehungen definieren die Erreichbarkeit von Lokationen im Transportnetz und werden durch drei Elemente definiert:

einen Startpunkt, der eine Lokation oder eine Transportzone sein kann
einen Zielpunkt, der ebenfalls eine Lokation oder eine Transportzone sein kann
ein Transportmittel

Ein Fahrplan stellt einen wiederkehrenden Transport dar, der einer vordefinierten Lokationssequenz folgt. Er kann zur Modellierung eines regelmäßigen Schiffs-, Luft-, Straßen- oder Schienenverkehrs verwendet werden und ist für einen bestimmten Zeitraum gültig. Fahrpläne werden zur Erstellung von Frachtdokumenten genutzt, die auf jeweils einer Fahrplanabfahrt basieren. Jeder Fahrplan gehört zu einer Fahrplanart.

In globalen Transportnetzen wird ein einzelner Transportauftrag in der Regel intermodal, d. h. über mehrere Verkehrszweige nacheinander ausgeführt. Der Wechsel des Verkehrszweigs findet an Umladelokationen statt, bei denen die Ware entladen und dann umgeladen wird.

Verkehrsbeziehungen (Trade Lanes) legen die grundlegenden geografischen Bezie hungen fest, die alle diese Business-Objekte strukturieren. Eine Verkehrsbeziehung kann sich auf einen Verkehrszweig und ein Transportmittel beziehen. Sie definiert eine Transportrichtung, die durch die Ausrichtung sowie eine Quelle und ein Ziel (beide sind entweder eine Lokation oder eine Zone) festgelegt ist.

Das Transportnetz-Cockpit ermöglicht die Darstellung des Transportnetzes oder von Teilen davon auf einer geografischen Karte sowie das Anlegen von Stammdatenobjekten wie Lokationen, Transportzonen und Verkehrsbeziehungen auf der Karte.

Ressourcen

Fahrzeugressourcen repräsentieren LKW, Anhänger, Lokomotiven und Waggons.
Transporteinheitsressourcen modellieren Seefracht- oder Luftfrachtcontainer
Fahrer
Kalenderressourcen stellen die Öffnungszeiten an den Lokationen dar.
Handlingressourcen verallgemeinern Kalenderressourcen und stellen zusätzliche zeitabhängige Kapazitätsrestriktionen dar, die z. B. die Anzahl der offenen Tore in einem Lager abbilden können.
Der Verkehrszweig definiert, welches Verkehrsmittel (z. B. Straße, Bahn, See und Luft) für den Transport verwendet wird
Das Transportmittel ist einem Verkehrsmittel zugeordnet und modelliert eine Klasse von Fahrzeugressourcen mit gleichen Grundeigenschaften, wie beispielsweise der Ermittlung von Entfernungen und Dauern oder der Definition von Planungskosten
Eine Fahrzeugressource ist einem Transportmittel zugeordnet und stellt eine Res source wie z. B. einen LKW, einen Anhänger, eine Lokomotive oder einen Waggon dar, die für die Planung und Ausführung genutzt werden kann.

Grundidee einer Equipmentart ist es, bestimmte Eigenschaften einmalig zu defi nieren, die dann von der Equipmentart in eine neue Ressource der jeweiligen Art ko piert werden (beachten Sie, dass Sie auch eine Ressource explizit kopieren können). Eine Equipmentgruppe ist eine Gruppierung mehrerer Equipmentarten mit dem Hauptzweck, sie zu strukturieren.

Transportkapazitätsmanagement

Mit dem Transportkapazitätsmanagement können Sie den Verbrauch der Transportkapazitäten Ihrer Spediteure lang-, mittel- und kurzfristig planen. So können Sie sich die Kapazitäten sichern, die Sie für Ihr Transportgeschäft benötigen, und die Transportkosten durch frühzeitige Reservierung reduzieren.

Frachtkostenabrechnung

LE-TRA Component (S4/ECC)

Transportation Planning Status (TRSTA)

Delivery is not to be processed in transportation planning. This is the case when:

the delivery type is not relevant for transportation, or
the route is not relevant for transportation (only for outbound deliveries; not required for inbound deliveries), or
a shipment block has been set in the delivery (only for outbound deliveries: not required for inbound deliveries)

Integration

Use integration of SAP ERP orders and deliveries to facilitate transportation planning and execution in SAP Transportation Management (SAP TM). The orders and deliveries are represented by transportation requirements in SAP TM.

Orders can be sent as order-based transportation requirements
SAP TM can generate a proposal for a delivery to be created in SAP ERP based on the order-based transportation requirement.
Outbound deliveries and inbound deliveries that are created in SAP ERP can be transferred to SAP TM, where they are stored as delivery-based transportation requirements.
While creating sales orders in SAP ERP, transportation scheduling can be done synchronously in SAP TM.
Integrate transportation planning in SAP TM with delivery and shipment processing in SAP ERP and warehouse planning and execution in SAP EWM.
If a product contained in an order or delivery is classified as dangerous goods, SAP TM considers this information to ensure a safe and compliant transportation of the product.

Customizing

Transportation Management> Integration>

Define Control Keys for Document Integration

Which documents in a document chain are to be integrated into Transportation Management (TM)

Define Transportation-Relevance of Sales Documents

When you create a sales document for which the integration has been activated, the system assigns the control key to the sales document (parameter TM_CONTROL_KEY) and to all relevant documents in the document chain (for example, the outbound delivery). This is a fixed parameter that cannot be changed subsequently in the sales document.

Scenario: Posting Goods Issue from TM

You cannot cancel the goods issue from TM. If it is necessary to cancel the goods issue this has to be done manually in ERP.

An outbound delivery has been sent from SAP ERP to SAP TM and a delivery-based transportation requirement (DTR) has been created in SAP TM.

In SAP ERP, the synchronous ERP inbound service OutboundDeliveryERPChangeRequestConfirmation_In_V1 is used to post a goods issue for an outbound delivery in ERP. In SAP TM this service is replicated as an outbound service: OutboundDeliveryERPChangeRequestConfirmation_Out_V1. This TM outbound service does not support the complete functionality of the ERP inbound service but only the subset needed for goods issue posting.

You can run the program /SCMTMS/POST_GI_BATCH to post goods issue to SAP ERP.

Scenario: Invoice integration

Use this integration scenario to transfer settlement documents from SAP Transportation Management (SAP TM) to SAP ERP to create billing documents or accruals.

#Service: Forwarding Settlement ( Customer Freight Invoice Request Processing )

Send Forwarding Settlement Request: SAP TM requests the creation, change, or cancellation of a billing document in SAP ERP. The billing document is based on a forwarding settlement document in SAP TM.
Create Customer Invoice: SAP ERP creates, changes, or cancels the billing document based on the request received from SAP TM. It then sends a confirmation to SAP TM.
Receive Forwarding Settlement Confirmation: SAP TM receives the confirmation and updates the corresponding forwarding settlement document. If SAP TM cannot process the confirmation, an error is triggered in SAP TM.

#Service: Freight Settlement

Send Freight Settlement Request: SAP TM requests the creation, change, or cancellation of accruals in SAP ERP (that is, the creation of a service purchase order and one or more service entry sheets). The accruals are based on a freight settlement document in SAP TM. SAP ERP also sends an update to SAP TM as soon as the corresponding supplier invoice has been posted.
Create Supplier Invoice: SAP ERP creates, changes, or cancels the accruals (that is, the service purchase order and one or more service entry sheets) based on the request received from SAP TM. It then sends a confirmation to SAP TM.
Receive Freight Settlement Confirmation: SAP TM receives the confirmation from SAP ERP and updates the corresponding freight settlement document.

#Service: Invoice Notification

Send Invoice Notification: SAP ERP sends a notification about the receipt of a supplier invoice to SAP TM.
Receive Invoice Notification from ERP: SAP TM receives the invoice notification and updates the posted amounts in the corresponding freight settlement document. If SAP TM cannot process the invoice notification, an error is triggered in SAP TM.

#Service: Invoice Simulation

Simulate Customer Invoice: SAP TM sends a new or changed forwarding settlement document or credit memo to SAP ERP and requests the transfer of data to preview the customer invoice or credit memo. SAP ERP returns the required data to SAP TM.
Simulate Forwarding Settlement Request in ERP System: SAP TM uses the data provided by SAP ERP to generate a preview of the customer invoice or credit memo.

Customizing

Integration with Other SAP Components> Transportation Management > Invoice Integration > Billing

Category codes, subcategory codes, and charge types in SAP ERP for the charge types from SAP TM: Integration with Other SAP Components Transportation Management Invoice Integration
Settings for Posting Forwarding Settlements

Condition types in SAP ERP for SAP TM charge types -> to post forwarding settlement documents from TM to create SD billing document in Sales and Distribution
Assign transportation charge element categories, transportation charge element subcategories, and transportation charge elements to condition types
Assign the credit memo reason code from the SAP Transportation Management (SAP TM) system to the order reason code in SAP ERP.

Settings for Posting Intracompany Settlements

Assign a transportation charge type in SAP Transportation Management (SAP TM) to a primary cost element mapping for intra company settlement processing in SAP ERP
Assign a Sender Organization which is a forwarding house as an organizational unit in Transportation Management (TM) to an internal order or cost center
Assign Internal Order / Cost Center to Receiver Organization

Integration with Other SAP Components> Transportation Management > Invoice Integration > Invoicing

Assign Service Master Record and Account Assignment Category: assign charge information from Transportation Management (TM) to a service master record and an account assignment category used for posting in Financial Accounting (FI).
Assign freight settlement document information from Transportation Management (TM) to purchasing information in Materials Management (MM). You can assign a freight settlement document type, freight settlement document category, and freight settlement document category description from TM to a purchasing document type, material group, plant, and purchasing group in purchasing.

Integration with Other SAP Components> Transportation Management > Invoice Integration > Tax

SD creates a billing item for a charge item, and applies tax to the billing item. In some countries, you may need to calculate tax for each charge type contained in each individual charge line in a charge item. To facilitate this, SD creates a billing item for each charge line in a settlement document when you enable tax for a country in SAP TM.
In TM you can have multiple charge types in a charge item. As standard, MM determines the tax code at the level of purchase order item or the individual service item.

Integration with Other SAP Components> Transportation Management > Invoice Integration > Mapping for Cost Distribution

The role you have in the transportation process determines how you should use the cost distribution feature. You can have the role of shipper or logistics service provider (LSP).

.....

You create a freight settlement document to transfer the transportation costs from SAP TM to SAP ERP for verification. You must perform cost distribution at the level of ERP item in the freight settlement document. You use service entry sheets and agency business documents to post the distributed costs in SAP ERP.

Invoice Preview Enhancement You can preview a final invoice in SAP Transportation Management (SAP TM) as it would appear in SAP ERP. The preview merges information from the relevant forwarding settlement document and tax information from SAP ERP.

Scenario: Order integration

#Service: Send Sales Order to Transportation Management System / Send Customer Return to Transportation Management System / Send Purchase Order to Transportation Management System

#Service: Send Delivery Proposal to SAP ERP (Outbound Delivery)

Send Outbound Delivery Proposal (as Bulk): SAP TM creates delivery proposals and sends them to SAP ERP to request the creation of the corresponding deliveries. In this step, multiple delivery proposals may be grouped into a bulk message to enable joint transmission, and to ensure that the delivery proposals are processed in the correct sequence and with sufficient levels of performance.
Create Outbound Delivery (as Bulk): SAP ERP sends a bulk confirmation to SAP TM, which contains individual confirmations for each delivery proposal in the bulk request that was received from SAP TM. If SAP ERP cannot process the complete request, an error is triggered in SAP ERP.
Receive Outbound Delivery Bulk Confirmation: SAP TM receives the bulk confirmation from SAP ERP and creates an entry in the application log. The application log entry includes the system messages that were created in SAP ERP during delivery creation, as well as the total number of deliveries created in SAP ERP and the ID of each delivery. If an error occurred during delivery creation in SAP ERP, SAP TM generates an alert. When a confirmation is received, SAP TM sets a confirmation timestamp in the relevant freight units.

#Service: Send Delivery Proposal to SAP ERP (Inbound Delivery)

Send Inbound Delivery Proposal: SAP TM creates delivery proposals and sends them to SAP ERP to request the creation of the corresponding deliveries. Note that inbound delivery proposals are sent using single messages; unlike outbound delivery proposals, which are sent using bulk messages.
Create Inbound Delivery: SAP ERP creates one or more inbound deliveries based on the delivery proposals received from SAP TM. SAP ERP might split a proposed delivery (for example, based on additional split criteria defined in SAP ERP). SAP ERP sends a confirmation to SAP TM. If SAP ERP cannot process the complete request, an error is triggered in SAP ERP.
Receive Inbound Delivery Confirmation: SAP TM receives the confirmation from SAP ERP and creates an entry in the application log. The application log entry includes the system messages that were created in SAP ERP during delivery creation, as well as the total number of deliveries created in SAP ERP and the ID of each delivery. If an error occurred during delivery creation in SAP ERP, SAP TM generates an alert.

#Service: Send SAP ERP Delivery to SAP TM

Send Outbound Delivery to Transportation Management System / Send Inbound Delivery to Transportation Management System: When an outbound delivery or inbound delivery is created, changed, or canceled in the SAP ERP system, SAP ERP sends the delivery to SAP TM.
Import Delivery from SAP ERP: SAP TM creates, changes, or cancels a delivery-based transportation requirement (DTR) based on the request received from SAP ERP. When SAP TM creates the DTR, the DTR consumes the transportation demand of the corresponding order-based transportation requirement or requirements, if applicable. That is, SAP TM determines the corresponding OTR items and reassigns the freight units to the DTR.

#Service: Split Outbound Delivery

Send Outbound Delivery Split: Based on planning changes, SAP TM requests that an outbound delivery is split in SAP ERP.
Split Outbound Delivery: SAP ERP splits the outbound delivery and sends a confirmation to SAP TM.
Receive Outbound Delivery Split Confirmation: SAP TM receives confirmation of the split from SAP ERP.

#Service: Update Outbound Delivery

Send Outbound Delivery Update: Based on planning changes related to changed dates, SAP TM requests that an outbound delivery is updated in SAP ERP.
Update Outbound Delivery: SAP ERP updates the outbound delivery and sends a confirmation to SAP TM.
Receive Outbound Delivery Update Confirmation: SAP TM receives confirmation of the update from SAP ERP.

Scenario: Scheduling of SAP ERP Sales Orders in SAP TM

A shipper can use this integration scenario to carry out transportation planning synchronously in SAP Transportation Management (SAP TM) during sales order processing in SAP ERP. This enables the transportation situation to be taken into account when calculating feasible dates and quantities for sales order items.

During order processing in SAP ERP, the transportation situation reflected in SAP TM is taken into account for calculating feasible dates and quantities for order items. This ensures that the sales order situation and the ATP situation are synchronized with the current situation in transportation.

Determination of transportation requirement type
Determination of freight unit building rule
Determination of planning profile

Customizing in ERP

Have activated the delivery and transport scheduling in Customizing for SAP ERP under Sales and Distribution Basic Functions Delivery Scheduling and Transportation Scheduling Define Scheduling by Sales Document Type.
Have maintained the standard ATP Customizing in SAP ERP under Sales and Distribution Basic Functions Availability Check and Transfer of Requirements.
the Sales Order Scheduling in SAP TM checkbox is selected

Schedule lines that were generated by a previous ATP check are removed.

The SAP TM scheduling service either schedules the material availability date backwards based on a given requested delivery date, or it schedules the delivery date forwards based on a given material availability date.

In addition to the material availability date and delivery date, SAP TM also determines the loading date, goods issue date, and transportation planning date.

During rescheduling, the system redistributes the available quantity according to the selection in the entry screen (transaction V_V2). For each sales order that is relevant for SAP TM, the system calls the SAP TM scheduling service within an ATP check.

#Service

The integration scenario comprises the following synchronous communication steps between an SAP ERP system and an SAP TM system in the same company:

Simulate Sales Order in Transportation Management System

While creating, changing, or rescheduling a sales order in sales order processing in SAP ERP, a shipper triggers sales order scheduling for the sales order items. SAP ERP sends the sales order data to SAP TM and requests the simulation of an order-based transportation requirement (OTR) and the related planning activities.

Simulate ERP Sales Order

When SAP TM receives the sales order data, it creates a temporary OTR, triggers transportation planning, and returns the planning results to SAP ERP. When SAP ERP receives the results of the simulation, it updates the schedule lines of the sales order accordingly.

EWM Basics

noreply@blogger.com (Dzmitryi Kharlanau) — Wed, 12 Jan 2022 12:34:00 +0000

Organisationsstruktur
Stammdaten
Bestandsverwaltung
Lieferabwicklung
Integration

You send a delivery to EWM but it does not reach EWM
3048632 - Information and restrictions for mobile data terminals in Warehouse Management in S/4HANA Cloud or EWM in S/4HANA On-Premise

Organisationsstruktur

Die wesentlichen Organisationselemente im SAP-ERP-System sind Mandant, Buchungskreis, Werk, Lagerort und Lagernummer. Über eine SAP-ERP-Lagernummer wird ein Lager als ein im EWM-System verwaltetes Lager definiert, was bewirkt, dass alle logistischen Belege wie An- und Auslieferungen im EWM-System repliziert werden.

In Verbindung mit EWM werden Ihnen häufig zwei Lagerorte begegnen: ROD steht für Received on Dock und AFS für Available for Sale. Im EWM-System werden Lagerorte auf der Benutzeroberfläche übrigens durch sogenannte Bestandsarten identifiziert. Ein Lagerort wird in EWM zunächst einer Verfügbarkeitsgruppe zugewiesen und die Verfügbarkeitsgruppe wiederum einer Bestandsart.

Wenn die Materialbelegposition für eine bestimmte Werk-Lagerort-Kombination angelegt wird, der eine SAP-ERP-Lagernummer zugewiesen worden ist, wird diese Lagernummer ebenfalls der Materialbelegposition zugewiesen. Wenn Sie z. B. eine Umbuchung mit den SAP-ERP Transaktionen MB1B oder MIGO anlegen, wird eine Lieferung angelegt und verteilt.

Die Organisationselemente unterhalb der Lagernummer sind insbesondere Lagertyp, Lagerbereich und Lagerplatz.

Neben Lagertyp, Lagerbereich und Lagerplatz gibt es weitere wichtige Organisationselemente in EWM, z. B. Bereitstellzonen, Arbeitsplätze und Tore

Customizing: Um sicherzustellen, dass eine im SAP-ERP-System angelegte Lieferung korrekt ins EWM-System verteilt wird, müssen Sie den Lieferungssplit für jede mit EWM verwaltete Lagernummer und für jede verwendete Lieferart erlauben. Wenn Sie diese Einstellungen nicht vornehmen, kann es sein, dass eine Lieferung nicht verteilt wird.

Versandstellen sind verantwortlich für die Abwicklung des Versands und gliedern die Verantwortlichkeiten im Unternehmen nach der Art des Versands, den notwendigen Versandhilfsmitteln und Transportmitteln

Wichtig ist, dass Sie auch eine Warenannahmestelle definieren

Lagertypen bilden die höchste Ebene der Organisationsstruktur unterhalb der Lagernummer.

General settings
Putaway control
Stock removal control
Goods movement control
Replenishment

Ein Lagerplatz (/SCWM/LS01 - Storage bin) ist ein getrennter Bereich im Lager, in dem ein oder mehrere Produkte gelagert werden können. Normalerweise liegen alle Lagerplätze eines Lagertyps im selben physischen Bereich des Lagers.

General data
Stock
Physical inventory
Bin Sectioning
Statistic
Activity areas
Warehouse tasks
PSA

Mithilfe einer Lagerplatzstruktur können Sie eine große Anzahl von Lagerplätzen schnell anlegen.

Eine Reihe von Lagerplätzen mit gleichen Eigenschaften kann zu einem Lagerbereich zusammengefasst werden. Lagerbereiche werden für die Einlagerung verwendet.

Wenn Sie einen Lagertyp mit festen Lagerplätzen pro Material (Fixlagerplätze) ( /SCWM/BINMAT, /SCWM/FBINASN ) haben, müssen Sie dem System mitteilen, welches Material auf welchem Fixplatz gelagert ist.

Ein Aktivitätsbereich ist eine logische Gruppierung von Lagerplätzen für eine be stimmte Aktivität (z. B. Kommissionierung, Einlagerung oder Inventur). Eine Anzahl von Lagerplätzen wird zu Aktivitätsbereichen zusammengefasst.

CLSP Cross-Line Stock Putaway
INTL Internal Movement
INVE Physical Inventory
NOLM Internal Movement Without Workload
PICK Stock Removal
PTWY Putaway
REPL Replenishment
STCH Posting Change

Die Zuweisung von Lagerplätzen zu Aktivitätsbereichen und damit auch die Sortierung der Lagerplätze immer abhängig von einer Aktivität ist.

Das Lagertor (Tor) ist ein Ort im Lager, an dem Ware das Lager erreicht oder verlässt. Die Tore befinden sich in räumlicher Nähe zu den zugehörigen Bereitstellungszonen.

Bereitstellungszonen sind Lagerbereiche, die innerhalb eines Lagertyps mit Rolle D liegen und dienen dazu, die Waren nach dem Entladen bzw. vor dem Beladen zwischenzulagern.

Wenn Sie mit Anlieferungen und Auslieferungen arbeiten, können Bereitstellungszonen für jede Lieferposition automatisch vom System gefunden werden – abhängig von den Materialien der Position

Ein Arbeitsplatz ist ein Bereich im Lager, in dem Aktivitäten mit Beständen oder mit HUs durchgeführt werden, wie z. B. das Verpacken und Umpacken, die Qualitätsprüfung, die Durchführung von LZL, die Zusammensetzung von Sets, die Dekonsolidierung oder das Zählen von Materialien. Sie können einen einzelnen Arbeitsplatz erstellen oder mehrere Arbeitsplätze zu einer Arbeitsplatzgruppe zusammenfassen..Jedem Arbeitsplatz ist ein Arbeitsplatz-Layout (auch Arbeitsplatz-Bildschirmkonfiguration genannt) zugewiesen. Arbeitsplatzermittlung.

Die Gegenstücke zur Versand- und Warenannahmestelle in SAP ERP sind in SAP EWM das Versandbüro bzw. das Wareneingangsbüro. -> Supply Chain Units (SCU)

Stammdaten

In SAP S/4HANA wird das Core Interface langfristig durch das DRF (Data Replication Framework) abgelöst.

Produkt

Global data: Die meisten Felder werden aus SAP ERP übernommen

Materialstamm – Massenänderung im EWM-Monitor ( SAP-Hinweis 223363 )

Um Produkte abhängig vom Lagertyp unterschiedlich verwalten zu können, ist es möglich, im Produktstamm unterschiedliche Lagertypsichten zu erstellen.

Geschäftspartner

Der Geschäftspartner sollte die ID-Typen für Kunden (CRM002), Lieferanten (CRM004) und Werk (CRM011)

Kundendaten. Daten, die für die Lagerprozesse relevant sind, sind die Adressinformationen (die auf Versanddokumente oder andere Formulare gedruckt und auch für die Routenplanung genutzt werden), die Identifikationsnummer und die Geschäftszeiten des Kunden , die z. B. zur Bestimmung des Warenausgangsdatums und der Auslieferzeiten genutzt werden könn

Ist der Kunde sowohl ein Auftraggeber als auch ein Warenempfänger, müssen nicht beide Geschäftspartnerrollen in EWM gepflegt werden. Für die Steuerung der Pro zesse in EWM reicht die Geschäftspartnerrolle Auftraggeber, die bei der Verteilung des Kunden über das CIF automatisch erstellt werden sollte.

Die Lieferantenstammdaten beinhalten, ebenso wie die Kun denstammdaten, die Basisinformationen des Lieferanten, inklusive des Lieferanten namens, der Lieferantenadresse, verschiedener Kontaktinformationen und verschie dener Daten, die im Allgemeinen nicht relevant für das Lagergeschehen sind (aber unter bestimmten Umständen nützlich sein können, etwa die Steuerklasse, Zahlungsdetails (z. B. Rückzahlungen) und die Statusinformationen).

Werke werden von SAP ERP über das CIF an EWM verteilt und automatisch in EWM mit den relevanten Rollenzuteilungen erstellt, sodass sie als Geschäftspartner für den Transfer von Ware zwischen Werken und für andere Aktivitäten genutzt werden können.

Andere Geschäftspartner: Mitarbeiter, Spediteur, Logistikkonsolidierer, Zollstelle, Wiederaufarbeiter.

Spply Chain Units (SCUs)

Spply Chain Units (SCUs) repräsentieren physische Orte oder organisatorische Ele mente in einem SCM-System, die von EWM genutzt werden, um die Lieferkette Ihrer Organisation vollständig abbilden zu können.

Werke
Kunden
Lieferanten
Versandstelle
MRP-Bereiche
Läger
Versandzonen
Transportdienstleister
Terminals oder Häfen

Jede SCU erhält Daten über ihre geographische Position, Geschäftspartnerbeziehungen, Zeitzone, Adresse und weitere Geschäftsattribute. Transaktionscode /SCMB/SCUMAIN.

Jedem Lager ist eine SCU zugewiesen. Transaktionscode /SCWM/LGNBP.

Sie können jeder SCU einen Kalender zuweisen. Sie können jeder SCU einen Kalender zuweisen.

Verpackungsmaterialien

Verpackungsmaterialien sind Materialien, die genutzt werden, um Produkte im Lager sicher und gruppiert aufbewahren zu können, damit der Transport der Produkte besser und schneller möglich ist. Hilfsverpackungsmaterialien sind Materialien, die gewöhnlich während der Vorbereitung für den Transport hinzugefügt werden, um die Materialien während des Transports zu schützen.

Packspezifikationen

Transaktionscode /SCWM/PACKSPEC

Zusätzlich haben Sie die Wahl, Packspezifikationsgruppen zu erstellen. Diese Grup pen erlauben Ihnen, Parameter zuzuordnen und unterschiedliche Strukturen für be stimmte Zwecke vorzudefinieren oder differenziert zu unterstützen.

Bestandsverwaltung

Ein Quant ist ein Bestandssegment einer bestimmten Menge eines Materials mit gleichen Eigenschaften. Quants werden im EWM-System durch Lagerbewegungen erstellt und gelöscht, etwa durch Wareneingänge, Warenausgänge, Umbuchungen oder durch Lageraufgaben.

Alle Quants eines Lagers bilden zusammen den sogenannten physischen Bestand dieses Lagers.

Sie können die Übereinstimmung weiterer Felder zusätzlich zur Übereinstimmung des Bestandsschlüssels beider Quants als Kriterium für eine Quantverschmelzung definieren

Transaktionscode /SCWM/MON

Bestandsführung auf Ressourcen Wenn Sie mit mobilen Endgeräten arbeiten, um Lageraufgaben im EWM-System zu quittieren, können Sie das System so einstellen, dass zu Beginn der Arbeit (z. B. beim Scannen einer HU) der Bestand auf die Ressource umgebucht wird. Bestand auf Ressourcen« heißt, dass dieser Bestand gerade bewegt wird. Extended Warehouse Ma nagement • Prozessübergreifende Einstellungen • Ressourcenmanagement • Queues definieren • Queues definieren.

Bestandsführung auf Transporteinheiten Während des EWM-Wareneingangsprozesses können Sie mit Transporteinheiten (TEs) arbeiten und Lieferungen sowie HUs einer TE zuweisen. Wenn Sie für eine TE den Wareneingang buchen, kann das EWM-System den Bestand auf diese TE buchen – anstelle des normalen Warenbewegungsplatzes. Extended Warehouse Management • Prozessübergreifende Ein stellungen • Warenannahme und Versand • Allgemeine Einstellungen • Steuerung von Warenbewegungen einrichten. Im Warenausgangsprozess gilt entsprechend: Es wird der verladene Bestand auf eine TE gebucht, wenn eine aktive TE der Auslieferung zugewiesen ist und das Verladen mit einem Ladeschritt der prozessorientierten Lagerungssteuerung durchgeführt wird.

Ebene des verfügbaren Bestands für HUs und für Chargen legen Sie unter dem Customizing-Pfad Extended Warehouse Management • Stammdaten • Lagertyp definieren fest

Logistics Inventory Management Engine

Insbesondere, wenn Sie das EWM-System erweitern müssen und Zusatzentwicklungen durchführen, sollten Sie wissen, was die LIME ist. Die Haupttabellen der LIME sind /LIME/NTREE (diese Tabelle beinhaltet die Bestandshierarchie in Form einer Baumstruktur) und /LIME/NQUAN (diese Tabelle enthält die Mengen für die Bestandsknoten). In der Tabelle /LIME/NTREE gibt es Basisknoten (ein Root, Typ R)..

Bestandsarten

Die automatische Umbuchung bei Quittierung von Lageraufgaben stellen Sie im Customizing über den Pfad Extended Warehouse Management • Stammdaten • Lagertyp definieren

Eigentümer, Verfügungsberechtigter und Besitzer

Dem Besitzer gehört das Lager, aber nicht zwingend auch der Bestand im Lager.
Der Verfügungsberechtigte ist die Partei, die über den Bestand verfügen darf. Der Verfügungsberechtigte ist immer der Geschäftspartner des SAP-ERP-Werkes.

Wenn Sie mit der Transaktion /SCWM/MAT1 die Lagerproduktsicht für ein Material pflegen, müssen Sie ebenfalls den Verfügungsberechtigten angeben

Der Eigentümer ist die Partei, der der Bestand gehört.

Chargenverwaltung

ithilfe von Auslieferungen kann die Charge wieder ausgelagert werden. Die Auslieferung kann die Charge entweder direkt aus dem SAP-ERP-System bekommen haben (als sogenannte vorgegebene Charge), oder sie kann im EWM-System vor der Kommissionierung angegeben werden.

Extended Warehouse Management • Prozessübergreifende Einstellungen • Chargenverwaltung • Verbuchungssteuerung (zentral, dezentral) einstellen.

Sie können Chargen in EWM anlegen, anzeigen und ändern. Wählen Sie dazu im SAP Easy-Access-Menü den Pfad Extended Warehouse Management • Stammdaten • Produkt • Chargen zum Produkt pflegen, oder rufen Sie die Transaktion /SCWM/WM_ BATCH_MAINT auf.

In EWM können Sie den Chargenzustand verwenden, um Wareneingänge und Wa renausgänge für Lieferpositionen zu verbieten.

Wenn keine Charge vorhanden ist, legt EWM eine neue Charge an, indem es den an fangs erwähnten Nummernkreis benutzt. Wenn EWM die Charge anlegt, werden die Werte der Anlieferposition in die entsprechenden Merkmale der Charge kopiert, u. a. das Herkunftsland, das MHD und das Herstelldatum. Business Add-Ins (BAdIs) /SCWM/DLV_BATCH_VAL bzw. /SCWM/DLV_ BATCH_CHAR verwenden.

Sie können sich die Chargenfindungskriterien in EWM anzeigen lassen, indem Sie in der Transaktion /SCWM/PRDO den Button Selektion oberhalb der Positionsübersicht anklicken.

Serialnummern

Im EWM-System gibt es drei Ebenen der Serialnummernpflicht:

A – Serialnummernpflicht für Belegposition

Serialnummern zu Lieferbelegen zu erfassen: zu einer Anlieferposition vor dem Wareneingang oder zu einer Auslieferposition vor dem Warenausgang.

B – Serialnummernpflicht auf Lagernummernebene

welche Serialnummern Sie gerade im Bestand haben, aber nicht wo (auf welchen Lagerplätzen) diese liegen oder welche Lagerbewegungen zu diesen Serialnummern durchgeführt worden sind.

C – Serialnummernpflicht in der Bestandsführung

die Serialnummern bei jeder Lageraufgabe und bei jedem Umpackvorgang angeben müssen

Handling Unit Management

Eine Handling Unit (HU) ist eine physische Einheit aus Packmitteln (Ladungsträger/ Verpackungsmaterial) und den darauf/darin gelagerten Materialien.

Sie können leere HUs entsorgen oder im Bestand halten und wieder benutzen.

Um HUs in EWM zu benutzen, müssen Sie das HUM in SAP ERP nicht aktivieren.

Sie können im Customizing für jede Packmittelart einstellen, ob das EWM-System eine leer gewordene HU dieser Packmittelart löschen soll oder ob sie leer im System verbleiben soll.

Extended Warehouse Management • Prozessübergreifende Einstellungen • Handling Units • Grundlagen • Packmittelarten definieren

Sie können festlegen, dass EWM während des Druckens ein Protokoll schreibt.

Seit dem Erweiterungspaket 2 (EHP 2) für EWM 7.0 ist es möglich, eine Verpackungs planung durchzuführen und auf diese Weise geplante HUs oder auch Plan-Versand HUs (PVHUs) zu erzeugen

Bestand auf Transporteinheiten

Eine Transporteinheit (TE), englisch Transportation Unit, ist die kleinste beladbare Einheit eines Fahrzeugs, die zum Transportieren von Waren verwendet wird.

Bestandsidentifikation (Stock ID)

Die Bestandsidentifikation (englisch Stock ID) ist eine eindeutige Nummer, über die ein Bestand, also ein Produkt, mit all seinen Bestandsattributen, z. B. Menge, Charge oder Bestandsart, angesprochen werden kann. er Hauptzweck der Bestandsidentifikation ist, dass sie während der Kommissionierung in einem EWM-Lager als Barcode auf ein Kommissionieretikett gedruckt wird und während des Wareneingangsprozesses in einem anderen EWM-Lager zur Vereinfachung des Wareneingangsprozesses genutzt wird.

Während der Kommissionierung erstellt das System Bestandsidentifikationen. (Delivery).

Sie drucken diese als Barcode auf dem Kommissionieretikett aus.

ie Warenausgangsbuchung wird ins SAP-ERP-System geschickt und dort verarbei tet. Die Bestandsidentifikationen werden als Teil der HU-Positionen von SAP ERP ge speichert (Feld VEPO-SPE_IDPLATE).

Das EWM-System kann Bestandsidentifikationen bei der Anlage von Lageraufgaben erstellen.

Das EWM-System löscht eine Bestandsidentifikation, wenn Sie Bestand in einen Lagertyp einlagern, der im Customizing das Kennzeichen Bestandsidentifikation löschen gesetzt hat. Alle Schnittstellenlagertypen (Arbeitsplätze, Tore, Bereitstellzonen) sollten Sie so einstellen, dass Bestandsidentifikationen erhalten bleiben.

Mindesthaltbarkeits- und Verfallsdatum

Die Lieferung wird akzeptiert, wenn die errechnete Restlaufzeit größer ist als die geforderte Mindesthaltbarkeit. Sie können dann den Wareneingang buchen. Wenn die Restlaufzeit kleiner ist, sperrt das EWM-System (je nach Einstellung) die Lieferposition und setzt einen »roten« Status, sodass das System die Wareneingangs buchung mit einer Fehlermeldung unterbindet.

Extended Warehouse Management • Prozessübergreifende Einstellungen • Chargenverwaltung • Einstellung für Lieferung – Lageranforderung vornehmen

Catch Weight Management

Hier kann das Gewicht eines Produkts von Stück zu Stück unterschiedlich sein, entweder aufgrund biologischer Unterschiede oder weil sich das Gewicht im Laufe der Zeit verändert. Diese Veränderlichkeit darf aber in einem Lagerverwaltungssystem nicht verloren gehen.

Mit CWM kann eine Unterscheidung zwischen der logistischen Mengeneinheit (z. B. Stück) und der Bewertungsmengeneinheit (z. B. Kilogramm) getroffen werden.'

Lieferabwicklung

Delivry type

GRN Benachrichtigung über erwarteten Wareneingang
EGR Erwarteter Wareneingang
IDN Anlieferungsbenachrichtigung
PDI Anlieferung
ODR Auslieferungsbenachrichtigung
PDO Auslieferungsauftrag
FDO Auslieferung
POR Umbuchungsanforderung
SPC Umbuchung
WMR Umlagerung

Die Lieferung unterscheidet verschiedene Terminarten, wie z. B. Liefertermine oder Transporttermine. Die Termine können von den SAP-ERP-Vorbelegen übernommen oder bei Belegaktualisierungen an diese übergeben werden

Item category

DLV Standardlieferposition
PAC Packmittelposition
RET Retourenlieferposition
TXT Textposition
VAL Wertposition (wird nur im Warenausgangsprozess verwendet)

Integration

You send a delivery to EWM but it does not reach EWM

/SPE/INB_DELIVERY_SAVEREPLICA, /SPE/OUTB_DELIVERY_SAVEREPLICA, LIKP-VLSTK

Use transaction SE38 to implement the attached correction report ZZRB_SET_VLSTK_FROM_B_TO_D_2. Pay attention to the test indicator when you execute the report. Only without this indicator does the system set the field LIKP-VLSTK for the specified delivery from "B" to "D" in the database. After this, you can use transaction VL06ID to send the delivery to EWM again.

3048632 - Information and restrictions for mobile data terminals in Warehouse Management in S/4HANA Cloud or EWM in S/4HANA On-Premise

The devices are connected to Wireless LAN via a wireless connection. Communication takes place in online mode only.
If function keys (for example, F1 to F12), you must implement SAP Note 3114046 and take into account its prerequisites.
Audio outputs, for example, in the case of errors or warnings, are not offered.
We recommend that you confirm your entries (in particular, by scanning bar codes) by pressing Enter. It is assumed that the bar code scanner automatically sends an "Enter" after scanning. Manual entries (for example, quantity entries) should be completed with "Enter". The tab key also switches the focus to fields that are not ready for input.
The tile Test RF Environment is released only for use in test systems in connection with desktop systems. Using the app from the Fiori shell is not supported on mobile devices. Normally, transactions on mobile data terminals should be reduced to the essentials - menu bars, status lines, and so on, would unnecessarily restrict the already small screens.

Additional

For more information about EWM deployment options, see SAP Note 1606493.

2623294 - How to correct EWM inconsistencies using report /SCWM/SR_INCONSTENCIES

You want to use the report /SCWM/SR_INCONSTENCIES to correct inconsistencies found in the Transportation Unit in /SCWM/TU.

Application Interface Framework (AIF)

noreply@blogger.com (Dzmitryi Kharlanau) — Fri, 07 Jan 2022 10:27:00 +0000

SAP Application Interface Framework is available for both cloud and on-premise systems. For on-premise systems, AIF is available as a part of the SAP S/4 HANA on-premise edition. If you want to monitor the custom interfaces you developed, you will need to purchase an additional license, AIFGEN.

Use cases:

Monitor, analyze, and correct interface errors
Separate technical and application integration

Overview

Value flow in Production

noreply@blogger.com (Dzmitryi Kharlanau) — Sun, 19 Dec 2021 17:05:00 +0000

Value flow in Sales

noreply@blogger.com (Dzmitryi Kharlanau) — Sun, 19 Dec 2021 17:05:00 +0000

Value flow in Procurement ( Beschaffungsprozess )

noreply@blogger.com (Dzmitryi Kharlanau) — Sun, 19 Dec 2021 17:04:00 +0000

Material group
Account determination
Commitments management

459509 - FAQ: Commitments in purchasing
68366 Aktive Verfügbarkeitskontrolle auf Kostenstellen

Material group

Eine Warengruppe ist eine Gruppierung von Materialien, für die unter Umständen keine Materialnummer vorhanden ist. Aus der Warengruppe kann auch eine Kontierung abgeleitet werden, sie unterstützt also eine automatisierte Verarbeitung.

Account determination

Die Bewertungsebene legt fest, ob die Kontenfindung für alle Werke eines Buchungskreises identisch ist oder ob Sie die Kontenfindung pro Werk ausprägen können. Das Werk als Bewertungsebene muss verpflichtend gewählt werden, wenn die Komponente PP (Produktionsplanung) oder die Produktkalkulation in CO genutzt werden sollen.

Die Bewertungsklasse können wir als Gruppierung der Materialien aus Sicht der MM-Kontenfindung verstehen.
Die Bewertungsklassen können Sie dazu zunächst zu sogenannten Kontoklassenreferenzen gruppieren.
Die Kontoklassenreferenzen werden wiederum den Materialarten zugeordnet

Commitments management

Purchase orders or purchase requisitions lead to financial commitments with varying degrees of obligation. Commitments reserve funds for costs that will be incurred at a future date. Therefore, commitments must be included in funds monitoring.

Commitments are created through purchase requisitions and purchase orders. Commitments are reduced by various business transactions such goods receipt. The commitments data is transferred to Controlling.

Creation of CommitmentsFor example, specific goods are ordered for an internal order, a cost center, or a project. A purchase order commitment is created that is equivalent to the purchase order value. The system executes all commitments in the currency used, in the original business transaction.
Reducing the Commitment. The commitment is reduced by business transactions (such as goods receipts) and actual costs are incurred by the corresponding account assignment object.
Carrying Forward Commitments at Year-End-Closing

Commitments Management distinguishes between three types of commitments, depending on the account assignment object:

Order Commitment: The commitment is initially assigned to an order.
Cost Center Commitment: The commitment is initially assigned to a cost center.
Project Commitment: The commitment is initially assigned to a project, or to a work breakdown structure element.

You activate commitments management:

For each controlling area from a chosen fiscal year
For orders per order type
For cost centers per cost center type

The following data is relevant to creating the PReq commitment:

The value of the purchase requisition
Planned delivery date
Account assignment

A purchase order commitment includes anticipated delivery costs. These costs are managed separately by the system. They are displayed individually according to origin (for example, freight costs, duty costs, packaging). This distinction between the delivery costs and the purchase order itself ensures that you can clearly display the different currencies in which the individual cost components are incurred.

The goods receipt indicator in the purchase order determines when the commitment is reduced and actual costs are set up (that is, in the detail screen for the purchase order item).

GR indicator set: Commitment is reduced when goods are received.
GR Indicator is not set: Commitment is reduced when invoices are received.

Depending on the account assignment object used, you can display commitments using the information system for Internal Orders, Cost Center Accounting, or for Project Systems.

Cost Center Accounting: Financials Controlling Cost Center Accounting Information System
Internal Orders: Financials Controlling Internal Orders Information System for Internal Orders
Projects: Financials Project System Project Information System

For documents with a valuated goods receipt, when setting the delivery completed indicator the commitments values should be totally reduced.

Stock transfer requisition and stock transfer order will not update commitment. From release 470, it's possible to handle commitments for stock transport requisitions/orders when BADI ME_COMMITMENT_STO_CH is active. Refer to note 604033.
For stock transfer orders, you need to make sure that the condition type which is commitment relevant is maintained.

459509 - FAQ: Commitments in purchasing

68366 Aktive Verfügbarkeitskontrolle auf Kostenstellen

Accounts Receivable (FI-AR)

noreply@blogger.com (Dzmitryi Kharlanau) — Sun, 12 Dec 2021 14:36:00 +0000

Features

Monitoring of receivables: overdue receivables and customer balances
Posting business transactions
Clearing of open invoices: post incoming payments and clear customer open items either manually or automatically
Evaluation of days receivable outstanding (DSO): identify customers with the highest or the lowest days receivable outstanding
Correspondence: sending correspondence (such as payment notices, open item lists, balance confirmation or account statements) to your customers
Periodic activities and closing operations: automatic payment, interest calculation or dunning
Analytics

Master data: manage and store your customer data as business partner data

A customer can be a person (individual), an organization or a group. A typical customer master data is made up of 3 areas (segments):

General Data
Company Code Data (FI area): account management, payment transactions, insurance, correspondence
Sales and Distribution Data (SD area)

Customizing

Financial Accounting > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data

Define Number Ranges

Assign Number Ranges to Customer Account Groups

Create Account Groups: You are already aware that an account group is used to control the creation of master records as it determines which fields have to be filled
Screen layouts
Define Accounting Clerks: ‘Customer: Correspondence’ tab - that the accounting clerk supervises
Define Industries
Define Sensitive Fields for Dual Control (Customers)

If you define a field (say, payment terms) in the customer (or vendor) master record as ‘sensitive’, then, the system blocks corresponding customer (or vendor) account for the payment run if there is a change to the entry.
use Transaction FD08 (for single records) and FD09 (for multiple customer master records) to view and confirm/reject the changes.

Report RFDABL00 to display changes to the customer master record data, across accounts.

Line Items

Financial Accounting > Accounts Receivable and Accounts Payable > Customer Accounts > Line Items

Define Period Types for Customers

Create account statements automatically by entering a key (say, 1 for monthly statements, 2 for quarterly statements, 3 for half-yearly statements and so on) specifying with which frequency the account statements are to be created in the ‘Bank Statement’ field in the customer master and ’Account Statement’ field in the vendor master records.

Balances

Maintain Worklist for Displaying Balances
Maintain Users and Accounts for Internet Services

Incoming Invoices/Credit Memos

Define Document Types

Differentiate between business transactions
Control the posting to the appropriate account types: the document type controls as to what type of account namely vendor, customer, or G/L, you can post to
Assign document numbers
Apply the vendor net procedure: the applicable discount and the net amount are calculated (and posted) when the vendor invoice is posted.
Financial Accounting > Accounts Receivable and Accounts Payable > Business Transactions > Incoming invoice

Define Posting Keys

Indicator, account type ( Customer/ Vendor/ G&L/ Assets/ Material ), Reversal, Payment transaction (?), Field status

Validation in Accounting Documents

Define ‘additional checks for accounting documents’ in the form of validations, for each of your company codes.

Define Default Values

Define the default document type and posting key for a Transaction

Define Field Status Variants

A ‘field status group’ (FSG) is a collection of field statuses, defined in the company code data of G/L account, and is used to determine which fields are ready for data entry input (required/mandatory or optional), and which needs to be hidden.

Assign Company Code to Field Status Variants
Define Subscreens for Coding Blocks
Screen Variants for Document Entry
Substitution in Accounting Documents: to replace of the field contents/ Transaction OBBH
Define Text IDs for Documents and Line Items: define text IDs for both document header and line items, to store additional or detailed information
Define Line Layout for Document Posting Overview: Transaction O7Z2
Define Line Layout for Document Change/Display: Transaction O7Z1
Select Standard Line Layout for Document Change/Display: Transaction O7V1
Document Change Rules, Document Header
Maintain Fast Entry Screens for G/L Account Items: Transaction O7V1

Open Item Clearing

An ‘open item’ is an uncleared transaction ( an unpaid invoice from a vendor) that can be cleared and closed, only when you post (a payment towards settling the vendor invoice) an offsetting amount to that account: when the offsetting amount is equal to the open item, then it is cleared in full; else, it is cleared partially as there is still a residual amount that is ‘open’.

For the open item, enter a due date for net payment, due date for cash discount, or deferral date; the system does not process (by dunning or payment program) that open item until that date is passed.

The account balance is always the total of the open items, as the sum of the items involved in any clearing transaction is zero.

Clear the open items either in the local currency (of the open item) or using a foreign currency. When cleared in a foreign currency, the system translates the transaction using the average rate between the two currencies: first translates the document currency into the local currency, and then translates the local currency using the clearing currency. The system posts those differences (beyond the tolerance limits) to the predefined G/L accounts.

If the payment differences are well within the tolerance limits, the system automatically adjusts the cash discount or posts the difference to a separate gain or loss G/L account.
If the payment difference exceeds the tolerance limits, you can, then, process the payment as a partial payment or enter a residual item for the difference:

When you enter a partial payment, the system does not clear the original receivable but posts the payment with an invoice reference.
When you create a residual item, the system clears the original receivable and posts the outstanding difference as a residual item to the customer account.

You can clear open item either manually or automatically using the clearing program.

Incoming payment: Financial Accounting > General Ledger > Document Entry > Incoming Payments
Outgoing payment: Financial Accounting > General Ledger > Document Entry > Outgoing Payments
Post with clearing: Financial Accounting > General Ledger > Document Entry > Post with clearing

To configure the system for open item clearing you need to complete the following tasks:

Define Accounts for Exchange Rate Differences
Define Account for Rounding Differences
Define Posting Key for Clearing Open Items
Make Settings for Processing Open Items
Prepare Automatic Clearing
Clearing Differences

Dunning

Make a (persistent) demand for a payment of an outstanding debt. The process of reminding your business partners (who are falling behind the payments) to pay the outstanding payment.

The program selects the overdue open items of an account, ascertains the ‘dunning level’ of the account and creates a dunning notice using the pre-defined dunning notice format and text, and finally saves the dunning data so determined for the line items / account which will be looked upon during the next dunning.

It is possible that you can dun a ‘one-time’ account as well, like any other account. While dunning the one-time accounts, the system groups all the items of a one-time account having the same address into a single dunning notice.

Dunning Procedure: You use the dunning procedure to control how the system carries out dunning. FBMP
Dunning Level: The system calculates the dunning level based on the number of days an open item is in arrears.
Dunning Area: A ‘dunning area’ is an organizational unit (for example, a division or sales organization etc) within a company code that you can use, as the responsibility area, for dunning.

Process

Creating Dunning Proposal
Editing Dunning Proposal: While editing a dunning proposal, you essentially carry out activities like setting / resetting the dunning blocks, and changing the dunning levels. You can manually increase or decrease the dunning level of an item or account in the proposal.
Printing Dunning Notices

Customizing

Define Dunning Areas: if there are different organizational units (distribution channel or business area or sales organization, for example) that are responsible for carrying out dunning within the company code
Define Dunning Keys: limit the dunning level for an item
Define Dunning Block Reasons: prevent an account or an item from being dunned
Define Dunning Forms

Accounts Payable (FI-AP)

noreply@blogger.com (Dzmitryi Kharlanau) — Sun, 12 Dec 2021 14:36:00 +0000

Features

Master data
Posting business transactions
Import of supplier invoices
Analysis of payments to suppliers
Management of cash discounts
Reviewing of cleared overdue invoices
Evaluation of days payable outstanding (DPO)
Management of payments
Management of payment blocks
Management of payment proposals
Management of payment media

ABAP development for Email sending

noreply@blogger.com (Dzmitryi Kharlanau) — Tue, 07 Dec 2021 09:07:00 +0000

Material valuation

noreply@blogger.com (Dzmitryi Kharlanau) — Mon, 15 Nov 2021 08:20:00 +0000

Stock posting
Revaluation postings
Negative stocks
Price differences and exchange rate differences
Transfer postings
Determination of the clearing entry during goods receipt for a purchase order
Determination of the debit entry of a goods receipt for a purchase order item with account assignment
Determination of the credit posting to order during a goods receipt for a production order

Stock posting

Value of the goods movement: With the majority of goods movements, a corresponding value flow is specified with the quantity flow. This goods movement value generally corresponds to the value from the stock posting (e.g. for consumptions); however, the value can also be determined via a purchase order price (goods receipt for purchase order), originate from the plan credit of a production order (goods receipt for production order) or simply be specified externally as a local currency amount (e.g. for a baseline inventory at the time of production startup).

For materials controlled by the moving average price, the stock posting is always determined proportionally to the value.
For standard-price-controlled materials, additions are posted proportionally to the price while withdrawals are posted proportionally to the value.

....

Formula for the value-proportional value determination:

Value of the stock posting = (total value of the stock * quantity) / total valuated stock

Formula for the price-proportional value determination:

Value of the stock posting = (standard price * quantity) / price unit

Revaluation postings

If a goods movement is posted in the previous period, the stock posting amount determined for the current period may differ from that in the previous period. If this is the case, you must create a revaluation document in the current period. Keywords for an SAP Notes search: UMB and MMVAL

0196505

Negative stocks

In the case of negative valuated stocks, particularly for materials controlled by moving average price, a special posting logic must be followed for the determination of the stock posting. Most important SAP Notes: 0196505Keywords for an SAP Notes search: BSX and MMVAL

Price differences and exchange rate differences

If the value of the good movement is different from the value of the stock posting, the difference is posted to a difference account regardless of whether it is a moving average price or standard price material.

During the goods receipt for a foreign currency purchase order, exchange rate differences can be posted
You post a goods receipt for a foreign currency purchase order without account assignment. Here, the system generates exchange rate differences and/or price differences.

Postings in local currency

Postings to the material stock account (BSX): GR quantity * standard price / price unit
during a reversal of a goods receipt: (Stock value * GR quantity) / total valuated stock

Postings to the GR/IR clearing account (WRX): Quantities of goods received are always valuated for the order price if an invoice does not yet exist for a quantity. However, if an invoice already exists for a GR quantity during goods receipt, goods receipt is valuated with the invoice price.

In foreign currency purchase orders, the valuation approaches in the purchase order or the invoices do not exist in local currency (they usually exist in purchase order currency). They are converted from the document currency into the local currency. The exchange rate of this translation can be determined at several positions.

The exchange rate can be fixed in the purchase order header. This specification has contract character with the vendor and means that the fixed exchange rate should apply to this purchase order, that is, independently of the exchange rate currently maintained in the system.
When an invoice is entered, an exchange rate is specified externally.

Exchange rate differences (KDM): The exchange rate differences result from the difference of the clearing value on the GR/IR clearing account (WRX) in document currency that is translated to the current exchange rate stored in the system in local currency from the clearing value in local currency that is determined with the conversion factor from the purchase order or the invoices.

(Price difference = GR/IR amount - stock value - exchange rate difference)

Price differences are posted to the GR/IR clearing account of the stock value if differences from the clearing value occur (for example, if the purchase order price differs from the standard price) or if an exchange rate difference posting is performed (in this case, price differences can also be posted for the moving average price materials).

Postings in document currency

Postings to the material stock account (BSX): the valuation in the material master in local currency (standard price, total value of stock) must be converted into document currency. This translation is carried out on the posting date with the exchange rate type that is assigned to the FI document type used, that is, independent from the exchange rate defined in the purchase order! If no exchange rate type is assigned to an FI document type, the system uses exchange rate type M.

Postings to the GR/IR clearing account (WRX): The same as for local currency posting.

Exchange rate differences (KDM): Exchange rate differences cannot occur in purchase order currency.

Price differences (PRD): Price differences are posted if the stock value in document currency does not match the clearing value in document currency.

If the goods movement is for a purchase order with account assignment, no PRD or KDM lines will be generated.

Transfer postings

For transfer postings, the value of the goods movement is determined from the stock posting of the issuing stock.
Most important SAP Notes: 0071124, 0180503
Keywords for an SAP Notes search: AUM and MMVAL

Determination of the clearing entry during goods receipt for a purchase order

During goods receipt for a purchase order, the value of the goods movement is determined using the clearing of the GR/IR clearing account. If a quantity is already calculated at the time of the goods receipts, the GR/IR clearing account is balanced proportionally, meaning the value of the goods movement is determined by the invoice value; if no invoice is available for the goods receipt quantity, the goods receipt is calculated using the net purchase order price or order price.
Delivery costs for goods receipts are also determined using this same clearing logic. However, the clearing posting is made to a separate account.
Most important SAP Notes: 1915844, 0049995, 0191927
Keywords for an SAP Notes search: WRX and MMVAL

Determination of the debit entry of a goods receipt for a purchase order item with account assignment

The total of the amount posted for the GR/IR clearing account and the provisions for the delivery costs (if they exist) are posted for the account assignment of the purchase order item.

Determination of the credit posting to order during a goods receipt for a production order

During a goods receipt for a production order, the value of the goods movement is determined by crediting the production order. If a quantity of goods received has not yet been calculated, the order credit is determined from the plan credit. If the quantity of goods received has already been calculated, the order is credited for actual costs.

FAQ

Goods movements in foreign currency ( 518114 )

Q: How is the goods receipt valuated for a purchase order in foreign currency?
A: During the goods receipt to a purchase order in foreign currency, the purchase order currency is the transaction currency.

Q: Which exchange rate is used during goods receipt for a purchase order in foreign currency?
A: If the flag 'Exchange rate fixed' is set in the purchase order, the system uses this exchange rate.Otherwise, the calculation is carried out with the current exchange rate for the posting date.

Q: How are exchange rate differences between purchase order date, goods receipt and invoice receipt dealt with?
A: Exchange rate differences and price differences can be displayed separately in the accounting document.You can set the point in time for the determination of exchange rate differences in Customizing of the invoice verification (Materials Management -> Logistics Invoice Verification -> Incoming Invoice -> Configure How Exchange Rate Differences Are Treated).

How does the system carry out the conversion of the currencies for the goods receipt for a purchase order if a material ledger is used?

1686557 - Unexpected exchange rate difference during goods receipt

Транзакция OMRW ( T169P Parameters, Invoice Verification )
Treatment of exchange rate differences in the company code currency.
If you set this selection field then the settings in the ERD Setting column for this currency type are no longer relevant.

The system calculates and posts exchange rate differences between order-related goods receipts and invoices not just for materials with standard price, but also for:

Materials with moving average price
Account-assigned transactions
Planned delivery costs

The valuation of the inventories or consumption is effectively done at the exchange rate for the goods receipt, and not at the exchange rate of the invoice. When you post the good receipts, the fixed exchange rate from the purchase order is not used, but the translation of the purchase order values to local currency is always done at the posting date of the goods receipt.

If you are using the material ledger with actual costing, the system does not include the posted exchange rate differences at period-end closing in the actual prices of the materials.

Customizing: in transaction OMRW "Treatment of exchange rate difference", the Field "ERD Setting" (table field T169P-XPLCU) is : blank
The fix exchange rate indicator in the purchase order (table field EKKO-KUFIX) is: blank
The currency in the purchase order is set, for example to USD
In transaction OBY6, the local currency is set to a different currency, for example to EUR
In transaction OB08, the related exchange rate is defined, for example to USD 1 = EUR 1.2347
A purchase order is created for example with 50 pieces of a material with an order price of 631.00 USD/piece, so the total PO amount is 31550.00 USD
Using the same example, the goods receipt shows a quantity of 50 pieces. The following exchange rate is stored at the time of the goods receipt in the system in transaction OB08: USD 1 = EUR 1.2347
Although the exchange rate hasn't been changed, the system will post to exchange rate difference account amounting to 0.01 EUR. This exchange rate difference is unexpected.

WRX	31.550,00-	USD	/	38.954,79-	EUR
KDM	0,00	USD	/	0,01	EUR

Due to compatibility reasons, the rounding caused by floating point value cannot be avoided. To avoid the exchange rate difference, you can split the quantity and carry out the partial goods receipt. In the above example, posting:

Goods receipt with quantity 1
Goods receipt with quantity 49

will lead to correct results.

Also the unexpected exchange rate difference generated by rounding can always be adjusted from FI side.

LMBGBFSU/ AUSGABE

Controlling

noreply@blogger.com (Dzmitryi Kharlanau) — Tue, 09 Nov 2021 12:14:00 +0000

Price change

Release future price

Basic knowledge
Additional information

1925393 - The priority to release the standard price

Price change

Release future price

Use the program SAPRCKM_PRCH.

746064 - CKME: Material master change document incomplete

When you release planned price changes by using Transaction CKME (Report SAPRCKM_PRCH), the system only saves the change of the current valuation price in the material master change document. By mistake, the system does not document the resetting of the 'Future price' (MBEW-ZKPRS) field and the 'Valid from' (MBEW-ZKDAT) field to initial values in the material master change document (see Transaction MM04).

Wichtige Strukturelemente

Gemeinkosten-Controlling (CO-OM)

(1) Kosten- und Erlösartenrechnung
(2) Kostenstellenrechnung
(3) Prozesskostenrechnung
(4) Gemeinkostenaufträge und -projekte
(5) Informationssystem

Produktkosten-Controlling (CO-PC)

(1) Produktkalkulation
(2) Kostenträgerrechnung
(3) Informationssystem

Ergebnis- und Marktsegmentrechnung (CO-PA)

Organisationseinheiten der Buchhaltung

Buchungskreis: Je Mandant können mehrere Buchungskreise definiert werden, allerdings muss mindestens einer eingerichtet werden. Der Buchungskreis ist sowohl die Mindest- als auch gleichzeitig die Hauptorganisationseinheit der Buchhaltung. Jeder Buchungskreis verwendet genau einen Kontenplan, während umgekehrt ein Kontenplan von mehreren Buchungskreisen genutzt werden kann. Ein Kon tenplan ist ein vom Rechnungswesen definiertes Gliederungsschema zur Aufzeichnung von Werten bzw. Wertströmen für eine ordnungsgemäße Rechnungslegung.
Gesellschaft: Eine Gesellschaft (auch Konzernunternehmen) ist eine Organisati onseinheit, für die ein Konzernabschluss aufzustellen ist. Eine Gesellschaft kann einen oder mehrere Buchungskreise umfassen
Geschäftsbereich: Der Geschäftsbereich stellt eine wirtschaftlich separate Einheit dar, für welche eine interne Bilanz sowie Gewinn- und Verlustrechnung erstellt werden können.

Organisationseinheiten der Kostenrechnung

Kostenrechnungskreis: Ein Kostenrechnungskreis ist die organisatorische Einheit innerhalb eines Konzerns, für die eine vollständige, in sich geschlossene Kosten rechnung durchgeführt werden kann.
Ergebnisbereich: Der Ergebnisbereich stellt einen Teil eines Unternehmens dar, für den eine einheitliche Segmentierung des Absatzmarktes vorliegt.

FAQ

1925393 - The priority to release the standard price

Mark the price under transaction CK40n which updated the field MBEW-ZPLPR as planned price under transaction mm03.
Also, mark the price under transaction CKMLCP which updated the field MBEW-ZKPRS as future price under transaction mm03.
Run Transaction code CKME or Transaction code CK24 to release the price.
Expect the price marked in transaction CKMLCP would be released as standard price but you found the price marked in CK40n was released.

2710853 - MIRO - Cost Center determination

In the OKB9 the Cost Center settings is done for debit exchange rate differences and profit centers for credit, per example. When the Invoice is posted by MIRO, the Accounting documents have the Purchase Order Cost Center. System does not consider the OKB9 settings.

Transaction OKB9 is just for default account assignments which means it is only considered if the interface (MM Invoice ) does not provide account assignment information to CO . In the other words, if in the Purchase Order exist a Cost Center in the Accouting assignment tab, this information will be considered in the lines WRX and KDM, per example. And in this case, the OKB9 settings will not have effect in the FI documents.

If it is required a different cost center in this scenario (Purchase Order with the information), this is only possible with a modification by making use of a substitution, as the one via transaction OKC9.

Tools to visualize

noreply@blogger.com (Dzmitryi Kharlanau) — Fri, 22 Oct 2021 17:32:00 +0000

Communication

BPMN Collaboration Diagram

Process description

BPMN Process Diagram
UML: Sequence Diagram

Data model

Class diagram
ERM diagram

Communication

BPMN Collaboration Diagram

A Collaboration represents the interactions between two or more business entities. A Collaboration diagram depicts a global point of view. It shows the interactions between participants in general.

Process description

BPMN Process Diagram

UML: Sequence Diagram

A sequence diagram is a type of interaction diagram because it describes how—and in what order—a group of objects works together.

Object symbol: Represents a class or object in UML. The object symbol demonstrates how an object will behave in the context of the system. Class attributes should not be listed in this shape.
Activation box: Represents the time needed for an object to complete a task. The longer the task will take, the longer the activation box becomes.
Actor symbol: Shows entities that interact with or are external to the system.
Option loop symbol: Used to model if/then scenarios, i.e., a circumstance that will only occur under certain conditions.
Alternative symbol: Symbolizes a choice (that is usually mutually exclusive) between two or more message sequences. To represent alternatives, use the labeled rectangle shape with a dashed line inside.
Lifeline symbol. Represents the passage of time as it extends downward. This dashed vertical line shows the sequential events that occur to an object during the charted process. Lifelines may begin with a labeled rectangle shape or an actor symbol.
Synchronous message symbol. Represented by a solid line with a solid arrowhead.
Asynchronous message symbol. Represented by a solid line with a lined arrowhead.
Asynchronous return message symbol. Represented by a dashed line with a lined arrowhead.
Delete message symbol. Represented by a solid line with a solid arrowhead, followed by an X.

Data model

Class diagram

Комментарии

Использование объектов классов другими объектами может быть описано через использование компонентов.

The class diagram shows the building blocks of any object-orientated system. Class diagrams depict a static view of the model, or part of the model, describing what attributes and behavior it has rather than detailing the methods for achieving operations.

A class is an element that defines the attributes and behaviors that an object is able to generate.

Class Notation

The notation that precedes the attribute, or operation name, indicates the visibility of the element: if the + symbol is used, the attribute, or operation, has a public level of visibility; if a - symbol is used, the attribute, or operation, is private. In addition the # symbol allows an operation, or attribute, to be defined as protected, while the ~ symbol indicates package visibility.

Static (underlined)

Interfaces

An interface is a specification of behavior that implementers agree to meet; it is a contract.

Associations

In UML models, an association is a relationship between two classifiers, such as classes or use cases, that describes the reasons for the relationship and the rules that govern the relationship. When you model a system, certain objects will be related to each other, and these relationships themselves need to be modeled for clarity.

An association is a linkage between two classes. Associations are always assumed to be bi-directional; this means that both classes are aware of each other and their relationship, unless you qualify the association as some other type.

Association class

In modeling an association, there are times when you need to include another class because it includes valuable information about the relationship.

Inheritance

It refers to the ability of one class (child class) to inherit the identical functionality of another class (super class), and then add new functionality of its own.

Aggregations ( consists of )

An association with an aggregation relationship indicates that one class is a part of another class. In an aggregation relationship, the child class instance can outlive its parent class.

The composition aggregation relationship is just another form of the aggregation relationship, but the child class’s instance lifecycle is dependent on the parent class’s instance lifecycle.

Nestings

A nesting is connector that shows the source element is nested within the target element.

ERM diagram (crow's foot)

An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how “entities” such as people, objects or concepts relate to each other within a system.

ER models and data models are typically drawn at up to three levels of detail

Conceptual data model: The highest-level view containing the least detail. Its value is showing overall scope of the model and portraying the system architecture. For a system of smaller scope, it may not be necessary to draw. Instead, start with the logical model.
Logical data model: Contains more detail than a conceptual model. More detailed operational and transactional entities are now defined. The logical model is independent of the technology in which it will be implemented.
Physical data model: One or more physical model may be developed from each logical model. The physical models must show enough

How to create

Purpose and scope: Define the purpose and scope of what you’re analyzing or modeling.
Entities: Identify the entities that are involved. When you’re ready, start drawing them in rectangles (or your system’s choice of shape) and labeling them as nouns.
Relationships: Determine how the entities are all related. Draw lines between them to signify the relationships and label them. Some entities may not be related, and that’s fine. In different notation systems, the relationship could be labeled in a diamond, another rectangle or directly on top of the connecting line.
Attributes: Layer in more detail by adding key attributes of entities. Attributes are often shown as ovals.
Cardinality: Show whether the relationship is 1-1, 1-many or many-to-many.