When the message of a PO is issued, in certain cases, the PO is issued in a mix of output language and another language. The aim should be that all elements of a PO are always printed in the message language. Just as it is the case with the formsin sales (invoice, etc.).
The transactions VA05 and also the VA05N should be extended by additional fields or customer-specific fields. Read more
In many companies there is now the requirement to mark products with a bar code of type GS1 Datamatrix directly from SAP. Unfortunately, the creation of a GS1 DataMatrix barcode is currently not supported in SAP standard. In particular, the FNC1 codes can not be inserted into a DataMatrix barcode. This fact is also indicated by the OSS note “1815093 – GS1 data matrix barcodes are not supported“.
In many SAP objects, Generic Object Services (GOS) can be used to link additional information to the object. In many cases, files (Word documents, Excel sheets), i.a. also graphics are uploaded to the object.
The following section describes how to read a graphic (BMP, JPG, PNG, …) for an SAP object and pass the binary content to the form to be displayed there.
In the data transfer routine when creating deliveries for sales orders, the delivery split can be executed according to various criteria. However, it is not possible to realize a split by quantity, i. that a material may only be put into a delivery with a certain or maximum quantity.
The software development process definition is one of the most neglected jobs in the SAP Competence Center’s area of responsibility. This job ain’t done by hiring of a few developers, particularly when they aren’t employees, but external freelancers.
It’s like a soccer team: There are several different roles, which must been taken on and there is a coach, who defines the tactics. The interplay of functional consultants, developers, key users, system administrators and – yes! – quality managers is as important as that each of them wants to do the best work they can, work that they can be proud of.
The packaging data are sent by EDI in a precisely defined structure to the automobile manufacturer. As a rule, the automobile manufacturer already provides the packing instructions. If the materials are then packaged physically, the labels are also printed. Important is that the data on the label are identical to the corresponding EDI data. When e.g. in the EDI data the unit has been transferred as package type 006280, the printer can not print 6280 on the label. That is, blanks and leading zeros in the EDI data are also to be printed on the label or coded in the barcode.
In certain cases, it is necessary to set the LZB indicator in the IDoc input INVOIC.
The LZB indicator is a mandatory field. The LZB indicator can be filled in userexit EXIT_SAPLIEDI_102 (extension FEDI0001).
The following is an example of coding:
In an SAP Adobe Forms form, the content of a field is to be displayed at a certain font height. However, it can be that the variable exceeds the size of the field when a certain number of characters are exceeded. In this case, the font height should be reduced. In the following a workaround […]
solidforms GmbH
Rudolf-Tarnow-Str. 25
17159 Dargun
Germany
Email: info@solidforms.de
Telephone: +49 (0) 39959-599810
Telefax: +49 (0) 39959-594999
