When considering macro representations always remember that even though the Data Portal may not have the exact part that you are looking for, it almost certainly has parts that are very similar to the part that you are looking for. These parts can be searched for using general search terms and used as a reference.
Now, as in everything in life, not all parts on the data portal are created equal. Some are excellent and some are a bit less than awesome and most will need some adjustments to make you happy, especially the NFPA designers.
Here are a few examples of various types of sensors and how a the graphical macro might differ based on the actual device construction:
EX1: Sensor or Device that is Field Wired
A device that requires point to point field wiring such as a limit switch.
Devices like this are often created without a graphical macro, instead they use the function template properties to define the available functions in the device. These functions then correspond to a standard electrical symbol for each function, in the case of a limit switch this might be a normally open and a normally closed contact.
If the designer instead chooses to create a graphical macro to represent the device, a window macro is often created that works well with the design style in use. At minimum this macro will often include a black box, a macro box and connection points of some sort.
Be sure to place the insertion points of the various connection points inside the macro black box or alternately include them in the macro selection.
These symbols represent wire connection points so remember to use device connection points, not terminals which look very similar.
Example Part: OMR.
(Includes Link to Data Portal)
EX2: A Device with a Plug Port
This is a very common representation of a sensor that is found in just about every project, it should be very clear that the sensor includes a plug port or receptacle (some here in the USA call this a Jack) and it should clearly represent that it is intended to mate to a plug on the end of a cable.
Make sure to get the plug symbol sex correct and make sure that the insertion points of the symbols are on or inside the black box.
The graphics shown here can be nice to have but they are not required, adding them can also make it harder to reuse them for other similar parts and its one more thing that can be identified at the end of the project that might need to be corrected.
Example Part: IFM.KI5085
EX3: A Device with supplied cable and fly leads
This represents a type of device that is commonly encountered that is provided with a length of multi-conductor cable. This device comes with factory terminated connections on the device side of the cable and loose or fly lead connections on the other.
Because a lead cable is provided with this part, it is important to illustrate that in the macro design so that it is clear to all (including yourself at a later date). In this case the designer created the black box and added device connection points with no graphics (hidden) to represent the direct wired connections. Standard symbols can also be added as graphics to help communicate the function and functions of the device.
Example Part: GAN.139.1-49-101-CK-2
Now like I said earlier, not all macros are created with the attention that they might deserve.
Just like the previous device this device also comes supplied with a length of cable. However if you only looked at the macro you might think that this is a field wired device with no supplied cable. I am not trying to shame anyone here, just want to point out that some methods are better than others for certain devices.
Example Part: A-
EX4: Device with included cable with Plug
In this example we have a device with an included cable with a factory terminated plug in which all the internal conductors are shown.. Now this is where you need to make a decision, do you show the internal conductors or not?
Most users would ever need to trouble shoot the internal conductors, so you may wonder why they are shown and decide not to show them yourself. However for EPLAN to be able to understand and communicate the full logic of the connections it needs the full details of all the connections. If you do not use or require these detailed capabilities you could also represent this connection as a single connection. For basic reporting purposes it will work fine, but once you go down this path you are committing to it and if you decide later to use error checking (EPLAN Messaging) you will find that EPLAN can tell that what you did graphically does not make sense logically.
Example Part: SICK.1072612
Here is a similar device with a macro that leaves room for confusion. Now logically the macro is correct and all device connections are shown, however you can probably imagine that most people who look at this macro would have no idea that the device includes a supplied cable.
Example Part: FES.570134
I hope this has been helpful for you.