All public logs

Combined display of all available logs of SAP Knowledge Base. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).

• 18:18, 8 January 2025 Unirab talk contribs created page Create and send e-mail with released class for cloud development (Created page with "category: code_snippets In all possible developments the released class "CL_BCS_MAIL_MESSAGE" should be used. In case the class is not available use the classic variant, see here. <syntaxhighlight lang="abap" copy> TRY. DATA(mail) = cl_bcs_mail_message=>create_instance( ). mail->set_sender( 'my@unirab.org' ). mail->add_recipient( 'r1@unirab.org' ). mail->add_recipient( iv_address = 'r2@unirab.org' iv_copy...")
• 14:02, 5 January 2025 Unirab talk contribs created page Virtual fields in CDS Views (Created page with "It is often necessary to supply data in a CDS view, as simple connections/relationships through CDS views are not possible and more complex coding is required. The calculation logic, in particular, is used to fill a field with a specific value. For performance reasons, you should use it as sparingly as possible. In my case, I developed an app with RAP and was able to map it completely using CDS views except for a few columns. == Introduction == Virtual fields are imp...")
• 13:36, 5 January 2025 Unirab talk contribs created page Variable and data binding in object with type 'Text'(AdobeForms) (Created page with "category: Forms category: Adobe Forms It is possible to store a variable with a specific data binding in an object with type “Text”, which only contains text. Because objects with type “Text” can actually only contain text. However, there are often requirements to insert a certain placeholder, i.e. a variable, into a text and to store this exactly with a data binding. This variable in the text is represented with curly brackets. Example: Dear ladies...")
• 13:33, 5 January 2025 Unirab talk contribs created page Category:Adobe Forms (Created page with "category: Forms Adobe Forms in SAP are used to design and generate forms for print, email, or other formats, often for documents like invoices, purchase orders, delivery notes, and payslips. Adobe Forms are based on the Adobe LiveCycle Designer, which is integrated with SAP to provide advanced layout and graphical capabilities. These forms allow for the customization and dynamic generation of documents with a flexible layout that can adapt based on the data received...")
• 13:29, 5 January 2025 Unirab talk contribs created page File:Access plant info record EKORG1.png
• 13:29, 5 January 2025 Unirab talk contribs uploaded File:Access plant info record EKORG1.png
• 13:28, 5 January 2025 Unirab talk contribs created page File:Access plant info record EKORG.png
• 13:28, 5 January 2025 Unirab talk contribs uploaded File:Access plant info record EKORG.png
• 13:18, 5 January 2025 Unirab talk contribs created page Purchasing Info Record (Created page with "== Overview == In the SAP system, the Purchasing Info Record (PIR) is a central element in the procurement process. It serves as a master data object that provides detailed information about the relationship between a supplier and a material. Essentially, the PIR is a combination of the vendor and material and contains information relevant to the purchasing process, such as prices, conditions, and delivery terms. Here’s a breakdown of the key components and importance...")
• 12:55, 5 January 2025 Unirab talk contribs created page How to use Cloud API PURCHASING SOURCE SRV for CRUD on sourcelist (Created page with "[[Category:Application_programming_interface] This wiki entry was written at the time of version 1.00 / last modified on November 14, 2024. * https://api.sap.com/api/API_PURCHASING_SOURCE_SRV/overview * https://help.sap.com/docs/SAP_S4HANA_CLOUD/bb9f1469daf04bd894ab2167f8132a1a/5692d23783a94d8282659356113c384f.html?locale=en-US == Create sourcelist == * HTTP-Methode: POST * /sap/opu/odata/sap/API_PURCHASING_SOURCE_SRV/A_PurchasingSource * HTTP-Request(Body) <syntaxhigh...")
• 13:48, 3 January 2025 Unirab talk contribs created page User:Unirab (Created blank page)
• 16:14, 31 December 2024 Unirab talk contribs created page Template:MetaDesc (Created page with "{{#description2:{{{1}}} }}")
• 17:53, 30 December 2024 Unirab talk contribs created page MediaWiki:Hf-nsfooter- (Created page with "56")
• 17:50, 30 December 2024 Unirab talk contribs deleted page MediaWiki:Bottom-notice-ns-0 (content was: "<hr /> <small> This is a private wiki created in the spare time of a single person working in the SAP ERP area.<br/> All products shown, including in the form of screenshots, belong to SAP SE.<br /> SAP SE [https://www.sap.com/about/legal/trademark.html trademarks] are: SAP®, ABAP®, SAP Business One®, SAP Fiori®, SAP HANA®, SAP NetWeaver®, SAP® R/3®, SAP S/4HANA®, SAP S/...", and the only contributor was "Unirab" (talk))
• 17:31, 30 December 2024 Unirab talk contribs created page MediaWiki:Bottom-notice-ns-0 (Created page with "<hr /> <small> This is a private wiki created in the spare time of a single person working in the SAP ERP area.<br/> All products shown, including in the form of screenshots, belong to SAP SE. <br /> </small>")
• 16:27, 30 December 2024 Unirab talk contribs created page User:Unirab/Timeless.css (Created page with "@import "https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-dark-mode.css&action=raw&ctype=text/css" screen and (prefers-color-scheme: dark);")
• 16:26, 30 December 2024 Unirab talk contribs created page MediaWiki:Timeless.css (Created page with "All CSS here will be loaded for users of the Timeless skin: @import 'https://www.mediawiki.org/wiki/Skin:Timeless-DarkCSS/timeless-dark.css?action=raw&ctype=text/css';")
• 15:40, 30 December 2024 Unirab talk contribs created page User:Unirab:Common.css (Created page with "@import "https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-dark-mode.css&action=raw&ctype=text/css" screen and (prefers-color-scheme: dark);")
• 16:20, 28 December 2024 Unirab talk contribs created page Monitoring IDocs with transaction code WLF IDOC (Created page with "Category:IDoc IDocs can be monitored and processed using the transaction 'WLF_IDOC'. The program offers many options in the selection screen to monitor or process only what is relevant to you or to the key user. You should perhaps hide some functions for the key user or restrict them through permissions, since depending on which target group uses the program, general users should not be allowed to use functions such as being able to change control records or change...")
• 14:38, 27 December 2024 Unirab talk contribs deleted page Category:In-App (content was: "#REDIRECT Category:In-App Extensibility", and the only contributor was "Unirab" (talk))
• 14:36, 27 December 2024 Unirab talk contribs moved page Category:In-App to Category:In-App Extensibility
• 14:17, 27 December 2024 Unirab talk contribs created page Category:RESTful application programming (Created page with "AP in SAP stands for Restful ABAP Programming Model, which is a modern framework for developing SAP Fiori apps and services in the SAP S/4HANA environment. RAP is designed to help developers create efficient, scalable, and cloud-native applications using the ABAP programming language while adhering to the principles of RESTful services and the SAP Fiori design guidelines. RAP is part of the broader initiative to enable the development of next-generation applications wit...")
• 14:07, 27 December 2024 Unirab talk contribs created page Category:Forms (Created page with "In SAP, forms are used to design and print documents that are generated during business processes, such as invoices, purchase orders, delivery notes, contracts, and other types of output. Forms allow businesses to format and present data in a way that is meaningful for end-users, while also adhering to legal or organizational standards. They are crucial for managing outputs from various SAP modules, such as Sales and Distribution (SD), Materials Management (MM), and Fina...")
• 14:03, 27 December 2024 Unirab talk contribs created page Category:Master data (Created page with "Master Data in SAP refers to the key business information that is used across different modules and processes within the SAP system. Master data is essential for the functioning of various transactions, and it serves as a foundation for processing and reporting business transactions. In essence, master data defines the objects that are central to business operations, such as customers, vendors, materials, and employees.")
• 13:36, 27 December 2024 Unirab talk contribs created page Category:IDoc (Created page with "An IDoc (Intermediate Document) in SAP is a standard data structure used for exchanging information between SAP systems or between SAP and external systems. It is commonly used in SAP for electronic data interchange (EDI), allowing data to be transferred between SAP and other systems, applications, or partners in a standardized format. Here’s an overview of what an IDoc is and how it works: 1. '''Purpose of IDoc''' - '''Data Exchange''': IDocs are used to transfer da...")
• 13:29, 27 December 2024 Unirab talk contribs created page Template:Links1 (Created page with "= Links = * {{{1}}}")
• 13:26, 27 December 2024 Unirab talk contribs deleted page Template:UsefulLinks (content was: "#REDIRECT Template:UsefulLinks1", and the only contributor was "Unirab" (talk))
• 13:26, 27 December 2024 Unirab talk contribs moved page Template:UsefulLinks to Template:UsefulLinks1
• 13:24, 27 December 2024 Unirab talk contribs created page Template:UsefulLinks (Created page with "= Useful links = * {{{1}}} * {{{1}}} * {{{1}}} * {{{1}}} * {{{1}}}")
• 13:23, 27 December 2024 Unirab talk contribs created page IDoc message type EXCHANGE RATE (Created page with "= General = '''Message type:''' EXCHANGE_RATE<br /> '''Basis type''' EXCHANGE_RATE01<br /> '''Direction:''' In / Out = Processing: Inbound IDoc = The following segment fields must be filled so that it can be posted: * RATE_TYPE * FROM_CURR * TO_CURRNCY * VALID_FROM * EXCH_RATE_V * FROM_FACTOR_V * TO_FACTOR_V Alternative * EXCH_RATE * FROM_FACTOR * TO_FACTOR")
• 13:16, 27 December 2024 Unirab talk contribs created page IDoc message type DESADV (Created page with "Category:IDoc The DESADV is the IDoc message type for delivery: shipping notification. The outbound IDoc can be used to transmit data from the delivery document and the inbound IDoc can be used to receive data, e.g. goods that the goods recipient partner has posted. = General = ''Message type:'' DESADV <br /> ''Basic type:'' DELVRY07 <br /> ''Direction:'' In and Out = Creation = == Outbound == Message control can be used to transmit the delivery to a partner. C...")
• 12:57, 27 December 2024 Unirab talk contribs created page IDoc message type MBGMCR (Created page with "Category:IDoc If a partner has carried out a goods movement or wants to transmit the goods movement to a partner in your system, this message type is suitable. = General = ''Message Type:'' MBGMCR<br /> ''Base type:'' MBGMCR0X<br /> ''Direction:'' Entrance & Exit = Creation: Output IDoc = == BAdI Usage == BAdI: MB_DOCUMENT_BADI<br /> Method: MB_DOCUMENT_BEFORE_UPDATE In the method, the FM create_outbound_IDoc_with_fm_MASTER_IDOC_DISTRIBUTE|MASTER_IDOC_DIST...")
• 12:47, 27 December 2024 Unirab talk contribs created page Document posting in finance with fm BAPI ACC DOCUMENT POST (Created page with "== Dependency: vendor or customer to G/L account line as well as S/H indicator == {| class='wikitable' |''Posting key for vendor/debitor line'' |''S/H indicator vendor/debtor line'' |''Posting key G/L account line'' |''S/H indicator G/L account line'' |- |01(customer) |S |50 |H |- |31(vendor) |H |40 |S |- |05(customer) |S |50 |H |- |11(customer) |H |40 |S |- |15(customer) |H |40 |S |- |21(vendor) |S |50 |H |- |25(vendor) |S |50 |H |- |35(vendor) |H |40 |S |} == Extensi...")
• 12:41, 27 December 2024 Unirab talk contribs created page Classic BAdI ACC DOCUMENT (Created page with "= BAdI use in relation to BAPI_ACC_DOCUMENT_POST and its extension parameter 'extension2' = == Create implementation in customer namespsace == The BAdI can be used multiple times and your own implementation can be created. Before you can save this, a filter must be assigned which reference process is relevant. With regard to the BAPI_ACC_DOCUMENT_POST, the reference process 'BKPFF' must be used here. For ma...")
• 12:34, 27 December 2024 Unirab talk contribs created page Classic BAdI FEB BADI (Created page with "The BAdI is called before the batch input folders are created with transaction FF_5 that carry out the postings. = Create implementation in customer namespsace = The BAdI cannot be used multiple times. According to an SAP note, the current implementation can be deactivated if the IBS Public Sector industry solution is not used. Alternatively, the customer exit 'FEB00001' can also be used. A Z-FM must be registered in the 'T_FEBCL' parameter of the exit FM, see more in...")
• 14:41, 26 December 2024 Unirab talk contribs created page IDoc message type MRESCR (Created page with "If data from the reservation is to be provided to a partner, the MRESCR can be used as a message type. For example, if the partner posts a receipt for the reservation, this can be received as a goods movement with message type [[IDoc_message_type_MBGMCR]. '''Message type:''' MRESCR<br /> '''Basis type:''' MRESCR0X<br /> '''Direction :''' Ausgang = Creation = Since it is an internal document, message control cannot be used. Therefore, the IDoc must be created with a...")
• 13:58, 26 December 2024 Unirab talk contribs created page Get exists and BAdIs from transaction codes and programs (Created page with "Category: code_snippets The following code can be used to display exits and BAdIs for a specific transaction code or program: Backup from https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/program-to-display-exits-and-badi/ba-p/12955380 <syntaxhighlight lang="abap" line copy> REPORT ZUSEREXIT . TABLES : TSTC, TADIR, MODSAPT, MODACT, TRDIR, TFDIR,...")
• 13:47, 26 December 2024 Unirab talk contribs created page Translations (Created page with "* Translate_objects_in_whole_transport_request")
• 13:47, 26 December 2024 Unirab talk contribs moved page Translate objectes in whole transport request to Translate objects in whole transport request
• 13:40, 26 December 2024 Unirab talk contribs created page Category:SAP Customizing Implementation Guide (SPRO) (Created blank page)
• 13:29, 26 December 2024 Unirab talk contribs created page File:Create new spro section step 3 1.png
• 13:29, 26 December 2024 Unirab talk contribs uploaded File:Create new spro section step 3 1.png
• 13:25, 26 December 2024 Unirab talk contribs created page File:Create new spro section step 3.png
• 13:25, 26 December 2024 Unirab talk contribs uploaded File:Create new spro section step 3.png
• 13:19, 26 December 2024 Unirab talk contribs created page Own section in the implementation guide (SPRO) (Created page with "= Step 1: Create IMG structure = The first step is to create your own IMG structure with a node using transaction code SIMGH. Additional nodes can then be created at the same or lower level: center|alt=create new SPRO section step 1 create IMG structure = Step 2: Create and assign IMG activity = Once the structure is in place, the respective IMG activities nodes can be inserted. As with nodes at the same or lower level: # An...")
• 13:19, 26 December 2024 Unirab talk contribs created page File:Create new spro section step 2.png
• 13:19, 26 December 2024 Unirab talk contribs uploaded File:Create new spro section step 2.png
• 13:13, 26 December 2024 Unirab talk contribs created page File:Create new spro section step 1.png
• 13:13, 26 December 2024 Unirab talk contribs uploaded File:Create new spro section step 1.png
• 12:59, 26 December 2024 Unirab talk contribs created page FioriApp:Create Billing Documents(F0798) (Created page with "category:Customizing_for_fiori_apps = Function "Display billig document after creation" = If this function is activated in the billing settings in the app, a temporary billing document will be created after selecting an item and clicking the 'Create invoices' button. If the number range prefix 'TMP' and the corresponding interval are not maintained in customizing, a error message appears. Note [https://launchpad.support.sap.com/#/notes/2922052/E 2922052] describes...")