#SAP Knowledge Message V1498 when creating credit memo request Message V1498 "Credit memo request already exists for item &1: &2 &3" when creating credit memo request
MICKAEL QUESNOT’s Post
More Relevant Posts
-
EXIT_SAPLV60B_008 User Exits Billing Document User Exit AC Interface Transfer Tables include zxvvfu08. Understanding EXIT_SAPLV60B_008 What is it? * A user exit in #SAP's SD module specifically for billing documents. * Focuses on the interface between sales and accounting during the billing process. * Allows customization of data transfer to accounting by modifying transfer tables.
To view or add a comment, sign in
-
SAP Message For Dummies No dunning settings have been maintained for company code Message no. F2090 Diagnosis You have tried to define dunning data in company code 1239 for the current account. Before you do this, however, you must define the company code data for company code 1239 within the dunning program configuration.
To view or add a comment, sign in
-
BTE 00001110 – CHANGE DOCUMENT: Save the standard data VS SAP FI Substitution Rule While both BTE 00001110 and SAP FI Substitution Rules can modify data in Financial Accounting, they operate at different levels and have distinct functionalities:
To view or add a comment, sign in
-
SAP T.CODES FOR R2R FS10N: GL Account display F.02 : GL Account posting with single journal. FB50 : GL Account posting with multiple. FB03 : To check the document number FB08 : Reverse document FBL5N: To check the customer line items FBL1N: To check the vendor line items FBL3N: To check to open line items OB52 : Books closure F.01 : Financial statement of Trial balance /OF.02: GL Account posting with new session
To view or add a comment, sign in
-
#SAP #FICO #Interview Electronic Bank Statement 🔔 📣 📢 🔊 Interview Question: Explain your experience on SAP EBS? Why do we need to assign external transaction types to posting rules? How does this configuration handle exceptions?🎵 🎶 🔦 💡 🪔 Answer: Answer: Exception handling is crucial! SAP allows configuration of fallback rules and error logs to manage mismatches. Example: If a customer payment doesn’t match any invoice, it might get posted to a suspense account. From there, the finance team can investigate and clear the item manually. Additionally: Errors like invalid transaction codes are captured in logs (e.g., SM13 for update errors), enabling quick troubleshooting.
To view or add a comment, sign in
-
#SAP #FICO #Interview Electronic Bank Statement 🔔 📣 📢 🔊 Interview Question: Explain your experience on SAP EBS? Why do we need to assign external transaction types to posting rules? How does this configuration handle exceptions?🎵 🎶 🔦 💡 🪔 Answer: Exception handling is crucial! SAP allows configuration of fallback rules and error logs to manage mismatches. Example: If a customer payment doesn’t match any invoice, it might get posted to a suspense account. From there, the finance team can investigate and clear the item manually. Additionally: Errors like invalid transaction codes are captured in logs (e.g., SM13 for update errors), enabling quick troubleshooting.
To view or add a comment, sign in
-
User_EXit Customer Enhancement in Data Segments Billing Document Output User-Exit SAPLVEDF Billing Doc-Outgoing EXIT_SAPLVEDF_002 ZXEDFU02 The EXIT_SAPLVEDF_002 user exit in SAP is a standard function module that provides a hook for customizing the IDoc processing of invoices. It's typically used to modify or enhance the invoice data before it's sent out as an IDoc.
To view or add a comment, sign in
-
SAP T.CODES FOR R2R PROCESS FS10N: GL Account display F.02 : GL Account posting with single journal. FB50 : GL Account posting with multiple. FB03 : To check the document number FB08 : Reverse document FBL5N: To check the customer line items FBL1N: To check the vendor line items FBL3N: To check to open line items OB52 : Books closure F.01 : Financial statement of Trial balance /OF.02: GL Account posting with new session /NEX : close the SAP logout. Or exit from login. #rtr #generalledger
To view or add a comment, sign in