The document provides configuration instructions for setting up warranty processing and authorization in SAP. It includes steps to define claim types, decision codes, processing statuses, action codes, validation rules, layout settings, and more. The configuration guide allows manual setup of these elements to enable warranty authorization functionality.
SAP Configuration Guide for Functional Modules (Based on IDES)sapdocs. info
Based on IDES, this configuration guide provides steps for functional modules of SAP like FI, MM and SD.
http://sapdocs.info/sap/sd-related-topics/sap-configuration-guide-for-functional-modules-based-on-ides/
Sap User Exit for Functional ConsultantAnkit Sharma
The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications.
User Exits is slot provided by SAP in SAP standard program.
User exits (Function module exits) are exits developed by SAP.
Code for the function module is written by ABAP Developer .
Developer does not write code directly in functional module , but in the INCLUDE that is implemented in the functional module.
SAP MM Configuration - Real Project Documentationsapdocs. info
Step by step configuration procedures for SAP MM module.. Screenshots, menu paths and descriptions provided
http://sapdocs.info/sap/materials-management-2/sap-mm-configuration-a-real-life-project-documentation/
SAP Configuration Guide for Functional Modules (Based on IDES)sapdocs. info
Based on IDES, this configuration guide provides steps for functional modules of SAP like FI, MM and SD.
http://sapdocs.info/sap/sd-related-topics/sap-configuration-guide-for-functional-modules-based-on-ides/
Sap User Exit for Functional ConsultantAnkit Sharma
The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications.
User Exits is slot provided by SAP in SAP standard program.
User exits (Function module exits) are exits developed by SAP.
Code for the function module is written by ABAP Developer .
Developer does not write code directly in functional module , but in the INCLUDE that is implemented in the functional module.
SAP MM Configuration - Real Project Documentationsapdocs. info
Step by step configuration procedures for SAP MM module.. Screenshots, menu paths and descriptions provided
http://sapdocs.info/sap/materials-management-2/sap-mm-configuration-a-real-life-project-documentation/
When good receipt (GR) and invoice receipt (IR) is performed, an accounting document gets generated. Movement of material leads to the automatic generation of accounting document and this is referred as MM FI integration.
Migrate Custom data/object in SAP S/4 HANA Ashish Saxena
S/4 HANA migration cockpit comes with preconfigured content and mapping for each migration object. For all major functional areas like product, customer, bank, profit centre, cost centre, plant, GL, etc. migration objects are predefined and their sequence and dependency is also defined.
As functional consultants, during implimentation we are facing a lot of problems to simplify O2C process and sales order entry its self. After a lot of research to simplify sales order entry process with out enhancement and modifications, find out certain functionalities that improve End user experience. Please share your experience, opinions and suggestions.
When good receipt (GR) and invoice receipt (IR) is performed, an accounting document gets generated. Movement of material leads to the automatic generation of accounting document and this is referred as MM FI integration.
Migrate Custom data/object in SAP S/4 HANA Ashish Saxena
S/4 HANA migration cockpit comes with preconfigured content and mapping for each migration object. For all major functional areas like product, customer, bank, profit centre, cost centre, plant, GL, etc. migration objects are predefined and their sequence and dependency is also defined.
As functional consultants, during implimentation we are facing a lot of problems to simplify O2C process and sales order entry its self. After a lot of research to simplify sales order entry process with out enhancement and modifications, find out certain functionalities that improve End user experience. Please share your experience, opinions and suggestions.
Here is the installation Guide of Sentrifugo-Open HRMS Software online
These Installation guide explains you the detailed process of how to install new version 2.0 beta which has many extra features than the previous one
It could be suitable for Windows,MAC,Android OS
For any support please mail us at : support@sentrifugo.com
This document provides details of all Sage CRM patch releases for version 7.2. Installing the most recent 7.2 patch (E) ensures that you get all of the fixes included in earlier patches (if applicable).
รายละเอียดเพิ่มเติ่มและโปรแกรม Sage CRM 7.2 Patch E Download กรุณาติดต่อ
ตัวแทนจำหน่าย Sage Software ในประเทศไทย
Sundae Solutions Co., Ltd.
โทร 026348899
Email: support@sundae.co.th
URL: http://www.sundae.co.th
In this system we will make extensive use of files system in C++.
We will have a login id system initially. In this system we will be having separate functions for
• Getting the information
• Getting customer information who are lodged in
• Allocating a room to the customer
• Checking the availability
• Displaying the features of the rooms.
• Preparing a billing function for the customer according to his room no.
In the software developed separate functions will be there for each of the above points so that there is ample scope for adding more features in the near future.
Download From Here : https://drive.google.com/folderview?id=0B5y_t4zL91BZaWRkY1VPeElJNVE&usp=sharing
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
2. Warranty Processing_Authorization_configGuide
Contents
Warranty Processing Enhancement: Configuration Guide.............................................................3
1 Purpose........................................................................................................................................3
2 Preparation..................................................................................................................................3
2.1 Prerequisites.........................................................................................................................3
2.1.1 Building Blocks................................................................................................................3
3 Configuration................................................................................................................................3
3.1 General Settings....................................................................................................................3
3.1.1 Defining Warranty Claim Type .......................................................................................3
3.1.2 Defining Decision Codes.................................................................................................8
3.1.3 Defining Processing Status.............................................................................................9
3.2 Defining Control Data..........................................................................................................10
3.2.1 Defining Warranty Action Code.....................................................................................10
3.2.2 Assigning Function Code to Action Code......................................................................12
3.2.3 Defining Action Controls for Authorization....................................................................13
3.2.4 Defining Copying Control for Authorization...................................................................15
3.3 Layout Settings....................................................................................................................16
3.3.1 Defining Pushbutton Profile..........................................................................................16
3.3.2 Defining Pushbutton Profile - Actions............................................................................18
3.4 Warranty Claim Settings......................................................................................................21
3.4.1 Assigning Decision Codes to Claimant/Reimburser......................................................21
3.4.2 Defining Message Class YEAT_VS..............................................................................22
3.4.3 Defining Validations......................................................................................................23
3.4.4 Activation of Vaildations/Substitutions..........................................................................45
3.4.5 Assigning Decision Codes to Messages.......................................................................46
3.5 Dealer Portal Setting...........................................................................................................46
3.5.1 Maintaining Profiles for Document ...............................................................................46
3.5.2 Maintaining Descriptions for Documents ......................................................................47
3.5.3 Creating Descriptions for Status...................................................................................48
3.5.4 Assigning Status .........................................................................................................49
Page 2 of 50
3. Warranty Processing_Authorization_configGuide
Warranty Processing Enhancement:
Configuration Guide
1 Purpose
This configuration guide provides the information you need to set up the configuration of this
building block manually.
If you do not want to configure manually and prefer an automated installation process using
eCATTs and BC Sets, use the SAP Best Practices Installation Assistant.
2 Preparation
2.1 Prerequisites
2.1.1 Building Blocks
Before you start installing this building block, the installation of the following building blocks must
have been completed:
Building Block Description
Baseline Project for Automotive In Sales client
A01 (Sales) Automotive Basic Settings
A05 (Sales) Master Data for Automotive
3 Configuration
3.1 General Settings
3.1.1 Defining Warranty Claim Type
Use
The purpose of this activity is to define the claim type used in warranty processing.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Claim Processing → Define Warranty Claim Types
Page 3 of 50
4. Warranty Processing_Authorization_configGuide
2. On the initial screen, choose New Entries.
3. On the Detail view screen, maintain the following data:
Clai
m
Type
Description Pricing
Schem
a
Messa
ge
Schem
a
Partne
r
Det.Pr
c
Reimburse
r Partner
Profile
Partner
Reimbu
rs.
Claiman
t
Partner
Role
YP02 BP Auto Claim
for
Authorization
WT000
2
WTY00
1
VN AS
Sales
Org
Distributi
on
Channel
Division Purch.
Organization
Version
Currency
Plant
Z001 Z1 Z1 Z001 EUR Z001
Layout
W/O Nav.
Tree
Layout
W Nav.
tree
Action
Control
Start
Process
Status
Start
Category
Field
Name Split
Criterion
Item Type
Group
SAPO SAP YP02 B001 IC HERST 00
Document Type Customer
Posting
Document Type Vendor
Posting
AcctDetProced
WP WR KOFI00
Page 4 of 50
8. Warranty Processing_Authorization_configGuide
Document Type Customer
Posting
Document Type Vendor
Posting
AcctDetProced
WP WR KOFI00
Result
Claim type is created.
3.1.2 Defining Decision Codes
Use
The purpose of this activity is to define decision codes.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Warranty Processing → Warranty Claim → Define Decision
Code
2. On the Change View “Decision Code”: Overview Screen, choose New Entries.
3. On the “New Entries: Details of Added Entries” screen, maintain the following data:
Field name Description User action and
values
Note
Decision 0001
Decision description Accepted
Decision 0002
Decision description Declined
Decision 0003
Decision description Partly Accepted
Decision 0004
Decision description Rejected
Decision 0005
Decision description In Review
Decision 0006
Decision description Authorized
Page 8 of 50
9. Warranty Processing_Authorization_configGuide
Result
The decision codes are created.
3.1.3 Defining Processing Status
Use
The purpose of this activity is to define actions processing status.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Warranty Claim Processing → Control Data → Process Control
→ Define Processing Statuses
2. On the initial screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, maintain the following data:
Processing Status Description of Process.Status Comment
B012 Claimant Version Created
B013 Claim Sent from claimant
Page 9 of 50
10. Warranty Processing_Authorization_configGuide
4. Choose Enter.
5. Choose Save.
Result
Processing status is created.
3.2 Defining Control Data
3.2.1 Defining Warranty Action Code
Use
The purpose of this activity is to define the actions used in warranty processing.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Claim Processing → Control Data → Process Control
→ Define Actions
2. On the initial screen, choose New Entries.
3. Maintain the following data:
Action Action Type Description Function
Module
Action
Sequence
YA67 F Elementary Action
Displayed in Action
Rel. IC-Version for
sending
Y_WTY04_
VER_IC_SE
Page 10 of 50
11. Warranty Processing_Authorization_configGuide
Box ND
YA61 F Elementary Action
Displayed in Action
Box
Copy Versions From
Claimant to Versions To
Reimburser
WTY04_DA
TA_SPLIT_I
C_OV
YA68 F Elementary Action
Displayed in Action
Box
To Versions (Claimant) WTY04_VE
RSION_CO
MBINE_IV_
OC
4. Choose Save.
Page 11 of 50
12. Warranty Processing_Authorization_configGuide
Result
The actions are defined.
3.2.2 Assigning Function Code to Action Code
Use
The purpose of this activity is to assign the function code to the action code.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Claim Processing → Control Data → Processing
Control → Assign Function Code to Action Code
2. On the “Change View: Assign Function Code to Action Code “Overview screen, choose New
Entries and enter the following data:
Field name User action and values Note
Function Entry in Command fld. YA67
Action YA67
Function Entry in Command fld. YA61
Action YA61
Function Entry in Command fld. YA68
Action YA68
Page 12 of 50
13. Warranty Processing_Authorization_configGuide
3. Choose Save.
3.2.3 Defining Action Controls for Authorization
Use
The purpose of this activity is to define actions controls.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Processing → Control Data → Process Control →
Define Action Controls
2. On the initial screen, choose New Entries.
3. On the New Entries: Details of Added Entries Screen, make the following records:
Field name Description User action and values Note
Action Control YP02 This value is for
A77
Action Control BP Auto Claim for Authorization
4. Choose Enter
5. Double-click Action Matrix, and on the Change View “Action Matrix”: Overview Screen,
maintain the following data:
Page 13 of 50
14. Warranty Processing_Authorization_configGuide
Action Control Start Processing Action Target Processing
YP02 A* B002
YP02 T* B002
YP02 B001 A* B002
YP02 B001 A008 B002
YP02 B002 A006 B003
YP02 B001 T* B002
YP02 B002 T* B002
YP02 B002 T060 B060
YP02 B003 A* B040
YP02 B003 T* B040
YP02 B003 T060 B060
YP02 B003 YA67 B040
YP02 B040 A* B040
YP02 B040 T* B040
YP02 B040 T060 B060
YP02 B040 YA67 B040
YP02 B060 T065 B040
6. Choose Save.
7. Repeat steps 2 to 6 for YP04 with the following data:
Field name Description User action and values Comment
Action Control YP04 This value is for
A77
Page 14 of 50
15. Warranty Processing_Authorization_configGuide
Action Control BP Auto Authorization Editor
Action Matrix:
Action Control Start Processing Action Target Processing
YP04 T* B005
YP04 B001 A300 B006
YP04 B001 T* B005
YP04 B005 A300 B006
YP04 B005 T* B005
YP04 B006 A301 B005
YP04 B006 T060 B062
YP04 B062 T065 B005
Result
The action controls are defined.
3.2.4 Defining Copying Control for Authorization
Use
Page 15 of 50
16. Warranty Processing_Authorization_configGuide
The purpose of this activity is to assign copy procedures to claim type.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Claim Processing → Control Data → Copying Control
→ Define Copy Procedures
2. On the initial screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, maintain the following data:
Claim
Type
Source
Categor
y
Target
Category
Copy
Profil
e
CopyMA
TPrice
CopyFRP
rice
CopySU
BLPrice
Comment
YP02 IC OC C1 X This value
is for A77
Result
Copy Procedures to Claim Type is assigned.
3.3 Layout Settings
3.3.1 Defining Pushbutton Profile
Use
The purpose of this activity is to create the pushbuttons on the warranty claim screen.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Claim Processing → Layout → Define Pushbutton
Profiles
2. On the initial screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, maintain the following data:
Pushbutton Profile Profile Description Action Control Comment
YP02 Authorization YP02 This value is for
Page 16 of 50
17. Warranty Processing_Authorization_configGuide
A77
Profile Action Control Category
YP02 YP02 IC Incoming Customer (IC)
YP02 YP02 OC Outgoing Customer (OC)
4. Repeat step 2-8 to make the following entries:
Pushbutton Profile Profile Description Action Control Comment
YP04 Authorization Editor YP04 This value is for
A77
Profile Action Control Category
YP04 YP04 IC Incoming Customer (IC)
YP04 YP04 OC Outgoing Customer (OC)
Page 17 of 50
18. Warranty Processing_Authorization_configGuide
Result
The Pushbutton profile is created.
3.3.2 Defining Pushbutton Profile - Actions
Use
The purpose of this activity is to create the pushbuttons on the warranty claim screen.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Claim Processing → Layout → Define Pushbutton
Profiles
Page 18 of 50
19. Warranty Processing_Authorization_configGuide
2. On the initial screen, select the Pushbutton Profile YP02 you have created in the previous
step.
3. Double-click Actions. On the Change View “Actions”: Overview Screen, choose New Entries,
and maintain the following data:
Function Action Code Text Pushbutton
W_BUTTON1 A008 IC Version Copy
W_BUTTON2 A006 VSR Check
W_BUTTON3 YA67 IC Release.
W_BUTTON4 A011 IC --> OC
W_BUTTON5 A860 OC Release.
W_BUTTON6 A041 Post to FI
Page 19 of 50
20. Warranty Processing_Authorization_configGuide
4. Choose Enter.
5. Choose Save.
6. Choose Back.
7. On the initial screen, select the Pushbutton Profile YP04 you have created in the previous
step.
8. Double-click Actions. On the Change View “Actions”: Overview Screen, choose New Entries,
and maintain the following data:
Function Action Code Text Pushbutton
W_BUTTON1 A300 Release
W_BUTTON2 A301 Reset Auth.
W_BUTTON3 T060 Close
W_BUTTON4 T065 Re-Open
Page 20 of 50
21. Warranty Processing_Authorization_configGuide
9. Choose Enter.
10. Choose Save.
11. Choose Back.
Result
The Pushbutton profile’s actions are created.
3.4 Warranty Claim Settings
3.4.1 Assigning Decision Codes to Claimant/Reimburser
Use
The purpose of this activity is to map data from the decision code, which transfers the reimburser,
to the decision code, which you communicate to the claimant.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
Page 21 of 50
22. Warranty Processing_Authorization_configGuide
IMG Menu Warranty Claim Processing → Warranty Claim → Assign
Decision Codes to Claimant/Reimburser
2. On the initial screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, maintain the following data:
DecisionReimburs Decision Claimant Note
0001 0001
0004 0004
Result
The decision codes are assigned.
3.4.2 Defining Message Class YEAT_VS
Use
Define your own message class and your message.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Tools → ABAP Workbench → Programming Environment →
Messages
Transaction Code SE91
2. In Message Maintenance: Initial Screen, in the Message Class field, input the new message
class YEAT_VS, then choose Create.
3. In Message Maintenance: Change Message Class Screen, Choose Attribute tab.
4. Enter "Automotive Warranty VSR Check" in the short text field.
5. In Message Maintenance: Change Message Class Screen, Choose Save.
6. In the dialog box Create Object Directory Entry, input $TMP in the Package field, and choose
Save.
7. In Message Maintenance: Change Message Class Screen, Choose Messages tab. Put the
cursor in the Message short text field in line 001.
8. Open the TXT file, Messages_YEAT_VS_UNICODE.txt, copy all the content of the txt file,
and paste the content in the screen.
Page 22 of 50
24. Warranty Processing_Authorization_configGuide
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Plant Maintenance and Customer Service → Warranty Claim
Processing → Control Data → VSR Check → Specify
Validations
2. In Change Validation: Overview screen, expand the first RE - General Contract under
Warranty folder.
3. Choose the first RE - General Contract, Choose Create Validation.
4. On the Create Validation: New Validation (Header Data) screen, maintain the following data:
Validation Name Description Message ID Comment
AMOUNT Amount Check YEAT_VS
5. Choose Enter.
6. Choose Save.
7. Choose Validation AMOUNT, choose Insert Step.
8. Choose Prerequisite under Step 001 folder.
9. Select the Table Fields tab, select Display technical name listed beside the tab block to
make sure you can see the tables with both the technical table name and the table short
description.
10. Double click WTY_RULE_AUTO_H (Interface for Rule Engine for Warranty Authorization
Header), then choose the field WTY_RULE_AUTO_H-VALIC (Amount Claimed) by double
clicking the line. Choose “>”, then choose Prev. Level to return to the table view. Double
click the table: WTY_RULE_H (Interface for Rule Engine for Warranty Claim Header), then
choose the field WTY_RULE_H-VALIC (Amount Claimed) by double clicking the line.
11. Check the formula displayed in the window it should be: WTY_RULE_AUTO_H-VALIC >
WTY_RULE_H-VALIC.
You can select from the menu: Setting → Short descriptions / Technical names to
switch the format displayed in the window.
12. Choose Back.
13. Choose Check under Step 001 folder.
14. Repeat Step 10-12.
15. Choose Save.
16. Choose Message under Step 001 folder.
17. Enter Message Type W and Message Number 010.
18. Choose Save.
Page 24 of 50
26. Warranty Processing_Authorization_configGuide
19. Choose the first RE - General Contract, Choose Create Validation.
20. On the Create Validation: New Validation (Header Data) screen, maintain the following data:
Validation Name Description Message ID Comment
AUTHOR Authorization Check YEAT_VS
21. Choose Enter.
22. Choose Save.
23. Choose Validation AUTHOR, choose Insert Step.
24. Choose Prerequisite.
25. Select the Table Fields tab,.
26. Double click WTY_RULE_H (Interface for Rule Engine for Warranty Authorization Header),
then choose the field WTY_RULE_H-AUTNO (Authorization) by double clicking the line.
Choose “<>”, then choose Constant.
Page 26 of 50
27. Warranty Processing_Authorization_configGuide
27. On the Enter constants: screen, leave the field Authorization blank and choose Enter. Choose
“OR”, then choose Prev. Level to return to the table view. Double click WTY_RULE_H
(Interface for Rule Engine for Warranty Claim Header), then choose the field WTY_RULE_H-
AUTNA (Authorizer) by double clicking the line. Choose “<>”, then choose Constant.
28. On the Enter constants: screen, leave the field Authorizer blank and choose Enter. Check
the formula displayed in the window. It should be: WTY_RULE_H-AUTNO <> ' ' OR
WTY_RULE_H-AUTNA <> ' '
You can select from the menu: Setting → Short descriptions / Technical names to
switch the format displayed in the window.
29. Choose Back.
30. Choose Check.
31. Repeat Step 25-29.
32. Choose Save.
33. Choose Message.
34. Enter Message Type E and Message Number 005.
35. Choose Save.
36. Choose Validation AUTHOR, choose Insert Step.
37. Choose Prerequisite.
38. Select the Table Fields tab.
39. Double click WTY_RULE_AUTO_H (Interface for Rule Engine for Warranty Authorization
Header), then choose the field WTY_RULE_AUTO_H-ASTATE (Processing Status) by
double clicking the line. Choose “=”, then choose Constant, and then input B006, choose
continue. Check the formula displayed in the window it should be: WTY_RULE_AUTO_H-
ASTATE = 'B006'.
You can select from the menu: Setting → Short descriptions / Technical names to
switch the format displayed in the window.
40. Choose Back.
41. Choose Check.
42. Repeat Step 38-40.
43. Choose Save.
44. Choose Message.
45. Enter Message Type W and Message Number 009.
Page 27 of 50
31. Warranty Processing_Authorization_configGuide
46. Choose Save.
47. Choose the first RE - General Contract, Choose Create Validation.
48. On the Create Validation: New Validation (Header Data) screen, maintain the following data:
Validation Name Description Message ID Comment
CLMTYP Claim Type YEAT_VS
49. Choose Enter.
50. Choose Save.
51. Choose Validation CLMTYP, choose Insert Step.
52. Choose Check.
53. Select the Table Fields tab.
54. Double click WTY_RULE_H (Interface for Rule Engine for Warranty Claim Header),
then choose the field WTY_RULE_H-CLMTY (Claim Type) by double clicking the
line. Choose “=”, then choose Constant, on the Enter constants: screen, input YP02
in field WtyClmType and choose Enter. Check the formula displayed in the window. It
should be: WTY_RULE_H-CLMTY = 'YP02'
You can select from the menu: Setting → Short descriptions / Technical
names to switch the format displayed in the window.
55. Choose Back.
56. Choose Save.
57. Choose Message.
58. Enter Message Type E and Message Number 004.
Page 31 of 50
33. Warranty Processing_Authorization_configGuide
59. Choose Save.
60. Choose the first RE - General Contract, Choose Create Validation.
61. On the Create Validation: New Validation (Header Data) screen, maintain the
following data:
Validation Name Description Message ID Comment
DATE Check Header Date YEAT_VS
62. Choose Enter.
63. Choose Save.
64. Choose Validation DATE, choose Insert Step.
65. Choose Check.
66. Select the Table Fields tab.
67. Double click WTY_RULE_H (Interface for Rule Engine for Warranty Claim Header),
then choose the field WTY_RULE_H-REFDT (Reference Date) by double clicking
the line. Choose “<>”, then choose Constant, and then on the Enter constants:
Page 33 of 50
34. Warranty Processing_Authorization_configGuide
screen choose Enter. Check the formula displayed in the window it should be:
WTY_RULE_H-REFDT <> ' '
You can select from the menu: Setting → Short descriptions / Technical
names to switch the format displayed in the window.
68. Choose Back.
69. Choose Save.
70. Choose Message.
71. Enter Message Type E and Message Number 002.
72. Choose Save.
73. Choose Validation DATE, choose Insert Step.
74. Choose Prerequisite.
75. Select the Table Fields tab.
76. Double click WTY_RULE_H (Interface for Rule Engine for Warranty Claim Header),
then choose the field WTY_RULE_H-REFDT (Reference Date) by double clicking
the line. Choose “<=”, then choose Prev. Level to return to the table view. Double
click WTY_RULE_H (Interface for Rule Engine for Warranty Claim Header), then
choose the field WTY_RULE_H-RELDT (Date) by double clicking the line. Check the
formula displayed in the window it should be: WTY_RULE_H-REFDT <=
WTY_RULE_H-RELDT
You can select from the menu: Setting → Short descriptions / Technical
names to switch the format displayed in the window.
77. Choose Back.
78. Choose Check.
79. Repeat Step 75-77.
80. Choose Save.
81. Choose Message.
82. Enter Message Type E and Message Number 001.
83. Choose Save.
84. Choose Validation DATE, choose Insert Step.
85. Choose Check.
86. Select the Table Fields tab.
87. Double click WTY_RULE_H (Interface for Rule Engine for Warranty Claim Header), then
choose the field WTY_RULE_H-REFDT (Reference Date) by double clicking the line. Choose
“>”, then choose Prev. Level to return to the table view. Double click
WTY_RULE_AUTO_H (Interface for Rule Engine for Warranty Claim Header), then choose
the field WTY_RULE_AUTO_H-REFDT (Reference Date) by double clicking the line. Check
Page 34 of 50
35. Warranty Processing_Authorization_configGuide
the formula displayed in the window. It should be: WTY_RULE_H-REFDT >
WTY_RULE_AUTO_H-REFDT
You can select from the menu: Setting → Short descriptions / Technical names to
switch the format displayed in the window.
88. Choose Back.
89. Choose Save.
90. Choose Message.
91. Enter Message Type I and Message Number 003.
Page 35 of 50
40. Warranty Processing_Authorization_configGuide
92. Choose Save.
93. Choose the first RE - General Contract, Choose Create Validation.
94. On the Create Validation: New Validation (Header Data) screen, maintain the following data:
Validation Name Description Message ID Comment
PARTNER Partner Check YEAT_VS
95. Choose Enter.
96. Choose Save.
97. Choose Validation PARTNER, choose Insert Step.
98. Choose Prerequisite.
99. Select the Table Fields tab.
100. Double click WTY_RULE_H (Interface for Rule Engine for Warranty Claim Header), then
choose the field WTY_RULE_H-PARNR (Partner) by double clicking the line. Choose “=”,
then choose Prev. Level to return to the table view. Double click WTY_RULE_AUTO_H
(Interface for Rule Engine for Warranty Claim Header), then choose the field
WTY_RULE_AUTO_H-PARNR (Partner) by double clicking the line. Check the formula
displayed in the window. It should be: WTY_RULE_H-PARNR = WTY_RULE_AUTO_H-
PARNR
You can select from the menu: Setting → Short descriptions / Technical names to
switch the format displayed in the window.
101. Choose Back.
102. Choose Check.
103. Repeat Step 99-101.
104. Choose Save.
105. Choose Message.
106. Enter Message Type E and Message Number 008.
Page 40 of 50
42. Warranty Processing_Authorization_configGuide
107. Choose Save.
108. Choose the secondary RE - General Contract, Choose Create Validation.
109. On the Create Validation: New Validation (Header Data) screen, maintain the following data:
Validation Name Description Message ID Comment
ACCEPT Accept Claim YEAT_VS
110. Choose Enter.
111. Choose Save.
112. Choose Validation ACCEPT, choose Insert Step.
113. Choose Check.
114. Select the Table Fields tab.
115. Double click WTY_RULE_H (Interface for Rule Engine for Warranty Claim), then choose the
field WTY_RULE_H-ASTATE (Processing Status) by double clicking the line. Choose “=”,
Page 42 of 50
43. Warranty Processing_Authorization_configGuide
then choose Constant, and then input B003, choose continue. Check the formula displayed in
the window it should be: WTY_RULE_H-ASTATE = 'B003'.
You can select from the menu: Setting → Short descriptions / Technical names to
switch the format displayed in the window.
116. Choose Back.
117. Choose Message.
118. Enter Message Type I and Message Number 006.
Page 43 of 50
45. Warranty Processing_Authorization_configGuide
3.4.4 Activation of Vaildations/Substitutions
Use
The purpose of this activity is to activate Vaildations/Substitutions.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics → Customer Service → Warranty Claim Processing
→ Master Data → Activation Validations and Substitutions
Transaction Code WTY_VSR_ACTIVE
2. On the initial screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
CoCod
e
Area Timepoi
nt
Valid Su
bs
t.
Valid
From
Vali
d To
Seq
uen
ce
Active Descriptn
US01 WY 1 AMOU
NT
Today Next
year
1
Active
Amount
Check
US01 WY 1 AUTH
OR
Today Next
year
1
Active
Authorizat
ion Check
US01 WY 1 CLMT
YP
Today Next
year
1
Active
Claim
Type
US01 WY 1 DATE Today Next
year
1
Active
Check
Header
Date
US01 WY 1 PART
NER
Today Next
year
1
Active
Partner
Check
US01 WY 1 ACCE
PT
Today Next
year
1
Active
Accept
Claim
4. Choose Save.
Result
Validations/Substitutions are activated.
Page 45 of 50
46. Warranty Processing_Authorization_configGuide
3.4.5 Assigning Decision Codes to Messages
Use
The purpose of this activity is to assign a decision code to specific messages that are the result of
validations.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Plant Maintenance and Customer Service → Warranty Claim
Processing → Control Data → VSR Check → Assign Decision
Codes to Messages
2. On the Change View “Assignment Message, Decision Code, Manual Processing”: Overview
screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Message Message Type Decision
010 I (Information) 0001
4. Choose Save.
3.5 Dealer Portal Setting
3.5.1 Maintaining Profiles for Document
Use
The purpose of this activity is to assign document types to the application IDs.
Procedure
2. Access the activity using one of the following navigation options.
Transaction Code SPRO
IMG Menu Discrete Industries → Business Package for Automotive
dealers → General Setting → Maintain Profiles for Document
3. Ignore the following information “Individual entries cannot be put request” By Enter.
Page 46 of 50
47. Warranty Processing_Authorization_configGuide
4. On the Change View “Document Profile”: Overview screen, choose New Entries.
5. On the New Entries: Overview of Added Entries screen, make the following entries:
Doc Pro (Document
Profile)
Doc. Type (Document Type) Doc Ret Ty
(Document Return Type )
3 YP01
3 YP02
6. Choose Save.
Result
The document types to the application IDs have been assigned.
3.5.2 Maintaining Descriptions for Documents
Use
The purpose of this activity is to assign descriptions to the document types.
Procedure
1. Access the activity using one of the following navigation options.
Transaction Code SPRO
IMG Menu Discrete Industries → Business Package for Automotive
dealers → General Setting → Maintain Descriptions for
Document
2. On the Change View “Value Table for Application ID”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the follow entries:
Field name Description User action and values Note
Doc. Type YP01 For Warranty
Lang. EN
Doc Desc. Description BP AUTO RECALL
Field name Description User action and values Note
Doc. Type YP01 For Warranty
Lang. DE
Doc Desc. Description BP Rueckruf
Field name Description User action and values Note
Doc. Type YP02 For Warranty
Lang. EN
Page 47 of 50
48. Warranty Processing_Authorization_configGuide
Field name Description User action and values Note
Doc Desc. Description AUTHORIZATION
Field name Description User action and values Note
Doc. Type YP02 For Warranty
Lang. DE
Doc Desc. Description Autorisierung
4. Choose save.
Result
The descriptions have been assigned to the document types.
3.5.3 Creating Descriptions for Status
Use
The purpose of this activity is to maintain a description for the status which you defined in the
IMG activity Assign Status.
Procedure
1. Access the activity using one of the following navigation options.
Transaction Code SPRO
IMG Menu Discrete Industries → Business Package for Automotive
dealers → Warranty Processing → Create Descriptions for
Status
2. On the Change View “Master Dealer Actions”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Web Status Lang. WTY Desc
05 EN WARRANTY CLAIM IS NEW
10 EN IN PROCESS
20 EN REJECTED
30 EN CLAIM SENT TO REIMBURSER
99 EN COMPLETE
4. Choose save.
Result
The description has been maintained.
Page 48 of 50
49. Warranty Processing_Authorization_configGuide
3.5.4 Assigning Status
Use
The purpose of this activity is to assign statuses for warranty processing in the Web to
(processing) statuses that exist in the DI system.
Procedure
1. Access the activity using one of the following navigation options.
Transaction Code SPRO
IMG Menu Discrete Industries → Business Package for Automotive
dealers → Warranty Processing → Assign Status
2. On the Change View “Mapping Front end to back end status”: Overview screen, choose New
Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Web status
(Status of claim on the web
interface)
Bck status
(Backend claim
status)
Decision
05 B001
10 B002
10 B003
10 B004
10 B010
10 B020
10 B025
10 B028
10 B030
10 B031
10 B040
10 B045
10 B055
10 B095
10 B095 0001
20 B050 0002
30 B010
99 B050 0001
99 B050 0001
Page 49 of 50