User contributions for Unirab

4 April 2025

• 15:2115:21, 4 April 2025 diff hist −9‎ Read on order stock - the sum of all open purchase order quantities for a material ‎No edit summary current

19 February 2025

• 13:5413:54, 19 February 2025 diff hist −3‎ Create application log in cloud development ‎ →‎Add messages current
• 13:5413:54, 19 February 2025 diff hist −3‎ Create application log in cloud development ‎ →‎Add messages

14 February 2025

• 16:1716:17, 14 February 2025 diff hist +128‎ Function modules and business application programming interfaces ‎No edit summary current
• 15:0915:09, 14 February 2025 diff hist −23‎ Read on order stock - the sum of all open purchase order quantities for a material ‎ →‎With Function Modules
• 15:0415:04, 14 February 2025 diff hist +27‎ Read on order stock - the sum of all open purchase order quantities for a material ‎No edit summary
• 15:0415:04, 14 February 2025 diff hist +4,358‎ N Read on order stock - the sum of all open purchase order quantities for a material ‎ Created page with "= Application = With transaction code MMBE you can read the on order stock for an material on plant level = Development = == With Function Modules == You can use FM "MM_GET_PURCHASE_ORDER_QUANTITY" to get the on order stocks for each positions in relevant purchase orders. Also you can use FM "MATERIAL_UNIT_CONVERSION" to convert the on order stocks in base unit of the material, e.g. to sum up all on order stocks for one unit and this should be the base unit of the mate..."

10 February 2025

• 10:5910:59, 10 February 2025 diff hist +58‎ IDoc message type PROACT ‎ →‎Outbound current

7 February 2025

• 22:5122:51, 7 February 2025 diff hist +182‎ IDoc message type PROACT ‎No edit summary
• 22:4822:48, 7 February 2025 diff hist +771‎ N IDoc message type PROACT ‎ Created page with "{{Template:MetaDesc|General information for the IDoc message type PROACT(sending stocks etc.) and how the inbound IDoc can be processed and how the outbound IDoc can be created.}} Category:IDoc The PROACT is the IDoc message type for stocks and requirements data in an SAP. The outbound IDoc can be used to transmit data to a supplier for VMI (Vendor Managed Inventory / SMI (Supplier Managed Inventory). == General == '''Message type:''' PROACT <br /> '''Basic type:''..."
• 22:3322:33, 7 February 2025 diff hist 0‎ Create job templates for Fiori App application job (F1240). ‎ →‎Y/Z class current
• 22:3322:33, 7 February 2025 diff hist −38‎ Create job templates for Fiori App application job (F1240). ‎ →‎Creating the required objects in ADT
• 22:3222:32, 7 February 2025 diff hist −52‎ Create job templates for Fiori App application job (F1240). ‎ →‎Creating the required objects in ADT

25 January 2025

• 15:0715:07, 25 January 2025 diff hist −4‎ MediaWiki:Hf-nsfooter- ‎No edit summary current
• 15:0715:07, 25 January 2025 diff hist −25‎ MediaWiki:Hf-nsfooter- ‎No edit summary
• 15:0715:07, 25 January 2025 diff hist +60‎ MediaWiki:Hf-nsfooter- ‎No edit summary
• 15:0515:05, 25 January 2025 diff hist −11‎ MediaWiki:Hf-nsfooter- ‎No edit summary

8 January 2025

• 19:3219:32, 8 January 2025 diff hist +1‎ Classes ‎ →‎E-Mail = current
• 19:3219:32, 8 January 2025 diff hist +393‎ Classes ‎No edit summary
• 19:2319:23, 8 January 2025 diff hist +79‎ Create and send e-mail with released class for cloud development ‎No edit summary current
• 19:2119:21, 8 January 2025 diff hist +125‎ Create and send e-mail with released class for cloud development ‎No edit summary
• 19:1919:19, 8 January 2025 diff hist +58‎ Create and send e-mail with released class for cloud development ‎No edit summary
• 19:1819:18, 8 January 2025 diff hist +1,176‎ N 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..."

5 January 2025

• 15:0715:07, 5 January 2025 diff hist −1‎ Virtual fields in CDS Views ‎ →‎Calculation logic current
• 15:0615:06, 5 January 2025 diff hist +1‎ Virtual fields in CDS Views ‎ →‎Calculation logic
• 15:0515:05, 5 January 2025 diff hist +15‎ Virtual fields in CDS Views ‎ →‎Calculation logic
• 15:0415:04, 5 January 2025 diff hist −1‎ Virtual fields in CDS Views ‎No edit summary
• 15:0415:04, 5 January 2025 diff hist +1‎ Virtual fields in CDS Views ‎No edit summary
• 15:0315:03, 5 January 2025 diff hist +144‎ Virtual fields in CDS Views ‎No edit summary
• 15:0215:02, 5 January 2025 diff hist +33‎ Virtual fields in CDS Views ‎No edit summary
• 15:0215:02, 5 January 2025 diff hist +5,849‎ N 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..."
• 14:4814:48, 5 January 2025 diff hist +34‎ Purchasing Info Record ‎No edit summary current
• 14:4814:48, 5 January 2025 diff hist +92‎ MediaWiki:Sidebar ‎No edit summary current
• 14:4614:46, 5 January 2025 diff hist +63‎ unirab.org:About ‎ →‎Statistics current
• 14:4214:42, 5 January 2025 diff hist +42‎ Category:Adobe Forms ‎No edit summary current
• 14:4214:42, 5 January 2025 diff hist −41‎ Category:Forms ‎ →‎Database tables current
• 14:4114:41, 5 January 2025 diff hist +6‎ Tables ‎ →‎Forms current
• 14:4114:41, 5 January 2025 diff hist +91‎ Tables ‎ →‎Forms
• 14:4014:40, 5 January 2025 diff hist +22‎ Category:Forms ‎No edit summary
• 14:4014:40, 5 January 2025 diff hist +55‎ Category:Forms ‎No edit summary
• 14:3914:39, 5 January 2025 diff hist +256‎ Tables ‎ →‎Forms
• 14:3614:36, 5 January 2025 diff hist +873‎ N 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..." current
• 14:3314:33, 5 January 2025 diff hist +503‎ Category:Adobe Forms ‎No edit summary
• 14:3314:33, 5 January 2025 diff hist +492‎ N 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..."
• 14:2914:29, 5 January 2025 diff hist +2‎ Purchasing Info Record ‎No edit summary
• 14:2914:29, 5 January 2025 diff hist +1,122‎ Purchasing Info Record ‎No edit summary
• 14:2914:29, 5 January 2025 diff hist +31‎ N File:Access plant info record EKORG1.png ‎No edit summary current
• 14:2814:28, 5 January 2025 diff hist +30‎ N File:Access plant info record EKORG.png ‎No edit summary current
• 14:1914:19, 5 January 2025 diff hist +32‎ Purchasing Info Record ‎No edit summary
• 14:1814:18, 5 January 2025 diff hist +6,036‎ N 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..."