POS outbound profile (Idoc type u0096 WP_PLU02)

Hi all
I have facing problem when I have flow data from sap to pos
Problem- there is one article that not listed to a site but when I m flowing article with the help of wpma Idoc of this article is also generated for the particular site and flow data to that site
I want if article is not listed to site then idoc will not generated
Idoc type WP_PLU02

Hi Justin,
key of the record WP_PLU IDoc is the article number and unit of measurement. This is always transferred with the main EAN/UPC (MARM-EAN11 in the article master data). All additional EAN (from table MEAN in the article master data) are transferred in the WP_EAN Message. There is no option to include additional EAN/UPCs into the WP_PLU IDoc.
This approach works well as long as the POS system uses a similar data model with PLUs (with the key of the main EAN/UPC) and cross reference UPCs in a separate table.
However if your POS system requires a PLU per EAN/UPC it would be necessary that the middleware between SAP Retail and POS creates these records as a combination of the WP_PLU and WP_EAN messages. In this case it would be required that the POS Outbound creates a WP_EAN message each time when a WP_PLU message is created and vice versa.
The creation of this additional message can be controlled by the Parameter TWPFI-EAN_ART.
Regards Carsten

Similar Messages

IS Retail POS Outbound

I was trying to understand the process of POS Outbound. I came to know that POS Condition Type Group should be created for telling the system that which condition types are to be moved to POS & in the same way POS Profile should be created.
Please let me know the steps to be followed after this. If possible in detail.
Regards,
Vamsi

Dear Vamshi,
For Outbound / Inbound,
(a) Define Logical system
(b) Port for IDoc processing
(c) Partner Profile
(d) Activate Message Types
(e) Define POS Outbound Profile
(f) Outbound Condition types
(g) Activate direct entry for creating worklist
Explore following parth for more details;
IMG - SAP Netweaver - SAP Web Application Server - IDOC Interface /Application Link Enabling - Basic Settings - Logical Systems - Define Logical Systems
SAP Menu - Tools - ALE - ALE Administration - Run-time Settings - Port Maintenance
IMG - Sales and Distribution - POS interface - outbound - Maintain profile for POS outbound
Bye,
Muralidhara

Sending price condition in WBBDLD for POS outbound

Hi experts
I am facing some problem when do configuration in order to send the price condition to POS through message type WBBDLD.
Client is using ZP01 tag price instead of VKP0 as the condition
Below are the config that I have performed but the price is not sending out.
1. (Sales and distribution --> POS interface --> outbound --> maintain POS condition type group) A new condition type group is created that replace VKP0 compared to the original SAP standard one.
2. (Sales and distribution --> POS interface --> outbound --> maintain profile for POS outbound) A new POS outbound profile using the above new condition type group
3. Site maintenance WB03, assign above new POS outbound profile to the specific store
4. (Logistics-general --> assortment --> assortment list --> controlling condition change analyses --> direct entry for creating the worklist --> activation of the direct entry for creating the worklist) tick "direct entry indicator" for 50 assortment list
5. (Logistics-general --> assortment --> assortment list --> controlling condition change analyses --> maintain filter setting for condition types) Add a new row for ZP01 for table no. 901
Really appreciate your advice.
BR
Dom

Hi Honghai,
Actually it's based on the customer pricing procedure. The default one is VKP001. If you assign the other customer pricing procedure in Tcode: OVKK, you should add the condition type to the corresponding pricing procedure.
Jessy

POS Outbound - sending multiple EANs per article in WP_PLU03

The configuration help on POS Outbound profile field TWPFI-EAN_ART (Indicator for article/EAN cross-reference) indicates that in this flag should be maintained when older POS systems are not able to accomodate a relationship between article number and UPC/EAN when multiple UPCs/EANs exist for an article.
Example: Article 4711 has UPC 123 and 456, both for UOM "EA". When the article is created and RWDPOSUP (TCode WPMU) or RWDPOSAN (TCode WPMA) is executed, two IDocs are generated: WP_PLU03 and WP_EAN01. However, I cannot use both IDocs as a source for my POS system's PLU. Instead, I want the WP_PLU03 to contain all UPCs/EANs for the article - in essence I would have two E1WPA01 segments for article 4711 - one for UPC 123 and the other for UPC 456. The help for this field, as I understand it, would do just this - however, enabling the configuration has no apparent effect, and in debugging the code, I cannot find where TWPFI-EAN_ART is taken into account during IDoc generation. Has anyone used this configuration before?

Hi Justin,
key of the record WP_PLU IDoc is the article number and unit of measurement. This is always transferred with the main EAN/UPC (MARM-EAN11 in the article master data). All additional EAN (from table MEAN in the article master data) are transferred in the WP_EAN Message. There is no option to include additional EAN/UPCs into the WP_PLU IDoc.
This approach works well as long as the POS system uses a similar data model with PLUs (with the key of the main EAN/UPC) and cross reference UPCs in a separate table.
However if your POS system requires a PLU per EAN/UPC it would be necessary that the middleware between SAP Retail and POS creates these records as a combination of the WP_PLU and WP_EAN messages. In this case it would be required that the POS Outbound creates a WP_EAN message each time when a WP_PLU message is created and vice versa.
The creation of this additional message can be controlled by the Parameter TWPFI-EAN_ART.
Regards Carsten

Outbound idoc types in XI

I was creating partner profile using we20 in XI to send and receives idoc of type ORDERS and ORDRSP. In the outbound parmtrs section I am not seeing ORDERS type. I clicked the + sign under the outbound parmtrs, it opened a new page to create a outbound paramets. I did not see ORDERS message type, so I created a message type called ORDERS and ORDRSP using we81. When I came back, I do see the message type I created. Now, I need to select the basic idoc type in the outbound options but I am not seeing ORDERS or ORDERS05 to select. Why isn't XI have the basic IDOCs for ORDERS.
Am I missing something?

Hi,
WE81 is the transaction for creating Logical Messag types in SAP R/3. Since XI is one of the R/3 product, you have an option to create the message types.
normally, Partner Profiles are maintained for Business communication in R/3 using EDI media. I am not sure, if at all XI will be used as a business partner as it is a middle layer kind of environment giving an interface facility to R/3 to the outside environment.
Coming to your question, XI need not to have all the message types/IDOC types as we see in R/3. IDOC Type definitions will be downloaded into XI for making it available for data transmission using the transaction IDX2 and is also known as IDOC CACHE.
To be able to help you out, let us know your scenario in which you are using XI as a business partner.
Further, Default Outbound parameters will not be available when a partner profile is created. You have to assign the business rules to it so called MESSAGE TYPES, IDOC TYPES, PROCESS CODES, RFCDESTINATIONS/PORTS, PACKET SIZES, MESSAGE CONTROLS. etc.,
What have you done? You have created a message type ORDERS/ORDERSP thru WE81, but no IDOC types are created.
Normal flow:
MESSAGE TYPE-->IDOCTYPE, PROCESS CODE
IDOC TYPE --> SEGEMENT TYPES
IDOC records are of three types. 1)Control Record holds the Sender/REceiver info, data header etc.,
2) Data record holds the data or body of message
3) Status record to hold the message status pre and post transmission.
All these makes a full cycle and is not an easy job to do buddy.
I am sure, nobody would want to create these in XI.
Let us all know what you were trying to achieve.
Good Luck,
Srini.

Outbound output type & Idoc type for MIRO (Invoice Posting)

Hi Gurus,
I have requirement like , I want to send the outbound IDoc to a external system containg the invoice detials after Saving in MIRO.
I am not able to find any output type & Idoc type for the same.
By going through varios threads , I found that there tell there is no Idoc type & output type for sending Idocs after MIRO.
Kindlt let me know, if it so, or how this req can be fullfiled by other ways.
Thanks
Amresh

Hi,
Create Custom Idoc type with required fields,custom output type and assign it to partner profiles.(If there is no std idoc type or output type)
Use Funtion module MASTER_IDOC_DISTRIBUTE to generate Idocs while saving MIRO, for this you need to find exit or implement implicit enhancement while saving MIRO.
Regards,
Ashok.

Outbound INVOIC idoc to partner type LS

Hello,
We are trying to issue outbound invoices( Message type INVOIC / basic type INVOIC02) to a 3rd party who will be doing the billing on our behalf. We are trying to issue an ALE output type to a LS (logical system) partner type and we are receiving a message B1131, that says that partner type LS cannot be used here, only KU and LI partner types allowed.
We can create the idocs if we setup our partner as a KU customer. However, given that we are sending these to a 3rd party system, it seems that we should be using LS. Does anybody know if there is some configuration where we can choose to be able to send an idoc of message type INVOIC to a partner type LS - logical system?
Thanks in advance.
Mark Monroe

Hi Mark,
For your requirement you, create partner profile for LS with following steps :
Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
Message Type : INVOIC
Under Outbound Option u2013 Tab
Receiver Port : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
Pack Size : 1
Transfer IDoc Immediately (Select)
Basic Type : INVOIC02
Cancel Processing After Syntax Error (Select)
Under Message Control - Tab
Application : V3
Message Type : RD00
Process Code : SD09
Hope, your problem will get resolve.
Regards..
Imran

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

IDoc type for Outbound Delivery

Hi All,
Can someone please tell me the IDoc type and message type to be used for creating the outbound delivery for an incoming IDoc? Also, I would like to know the function module.
Regards,
Raghav

Hi,
Message type is DESADV
Basic type is DELVRY01 to 03 (can check the latest version or supported version)
Function module : BORES_IDOC_INPUT_DESADV1 or IDOC_INPUT_DESADV1
This is used for creating outbound deliveries, shipping noticfication etc.
Regards
vk

IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver

Hi ,
We have a requirement where we have to send Inbound delivery confirmation as well as outbound delivery notification to our same customer. (3PL case)
We have a EDI partner who is receiving our messages and transforming them before sending it to customer.
Now my problem is , since I am using same idoc type (DELVRY03) for both cases therefore wondering how my EDI partner will differentiate whether received message is a INBOUND delivery confirmation or OUTBound delivery notification.
regards
Shrey

Thx for your reply ...
Wondering about the impacts , if I create a new message type like ZDESADV and attach it to DELVRY03.
In this i could have two message types DESADV and ZDESADV.
Will it impact anywhere ?
Regards
Shrey

Outbound FM For CLFMAS01 Idoc Type

Hi Frnds,
My Requirement is Need to send classtype 001 details to CRM from ECC..using CLFMAS01 Idoc Type.
but i am unable to find out the Outbound Function Module..Please help to find that one.
Thanks,
Laxmi

Hi ,
As per ECC6 , the above FM is exist and also maintained in BD51 and WE57 for same message type.
Just recheck the same. If the FM Exist in the system them you can configure the same in BD51 and WE57 .
Thanks
Subhankar

What is outbound function module for IDoc type INFRECMASS01

Hi,
What is outbound function module for IDoc type INFRECMASS01? This is for purchasing info record.
Thanks
Kamal

Hi Kamal,
Have you looked standard program RBDSEINF or transaction code ME18?
This program will call function module MASTERIDOC_CREATE_REQ_INFREC to generate purchasing info record IDoc.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Where we will attach the Idoc type to outbound FM

HI All,
Here we are using Idoc type as ORDERS05 for one ALE scenario, i am sure that outbound FM is 'IDOC_OUTPUT_ORDERS'. But like to know in which transaction we will attach the IDoc type & message type to this function module.

Hi,
If ur using standard idoc then no need to attach ur function module with message type or basic type.But if u r using a customized message type and basic type then u should attach IN BD60(tcode).
Regards,
Nagaraj

Test Outbound Idoc type DELVRY01

Hi all,
We've a client who is presently using idoc type DESADV/DELVRY01 for sending Orders outbound. They want to modify the existing output data, which I've deduced I can do by using an existing user exit (.
But when I use WE19 to test the outbound process, ALE is not stopping at my break-point. Can any tell if I'm doing anything wrong with my testing process? How can I get the outbound idoc to stop?
Points rewarded for useful answers.
Cheers,
Steve

Hello Stephen,
WE19 is for testing for Inbound IDOC..
If you want to test Outbound IDOC ,you need to create delivery or change the delivery in VL01N or VL02N Transaction.
Here you need to give correct output type like Delivery transaction output would be LD00 -> you can find out Delivery Output type in NACE Transaction.
GOTO NACE -> select V2 Application -> Click on output type -> here you are able to see all output types
if you don't find output type then contact Functional guy.
once you create delivery it will create IDOC ,you can IDOC Status in WE02 Transaction.
if you want to debug IDOC then follow below Steps :
goto delivery transaction -> when you create delivery ,please modify output type -> extras -> header -> output type
here see the further data -> select peridocally scheduling.
now come to RSNAST00 Program
enter delivery number as object number
Application -> V2
Output type -> enter delivery output type
Medium - A (ALE) ,6(EDI)
Now you are able to work on debugging
Thanks
Seshu

Idoc types and message types we use in IS-Retail

hi gurus,
can anyone tell me what are the idoc types and their message types that we use in SAP IS-Retail .
Thanks in advance
regards
gopal

Hello, these are the main idoc types used in sap retail:
'WPDBBY01' POS outbound: bonus buy conditions
'WPDCUR01' POS interface: Download exchange rates
'WPDNAC01' POS interface: Download products
'WPDSET01' POS interface: Download set assignments
'WPDTAX01' POS interface: Download tax rates
'WPDWGR01' POS interface: Download material group master
'WPUBON01' POS interface: Upload sales docs (trnsctns), non-aggregated
'WPUERR01' POS interface: Upload messages SRS/POS/SCS
'WPUFIB01' POS interface: Upload Fin.Acc. interface SRS/POS
'WPUKSR01' POS Interface: Inbound processing cashier data for POS stats
'WPUTAB01' POS interface: Upload day-end closing POS
'WPUUMS01' POS interface: Upload sales data (compressed)
'WPUWBW01' POS interface: Upload goods movements
'WP_EAN01' POS interface: Upload/Download EAN assignments
'WP_PER01' POS interface: Upload/Download person data
'WP_PLU01' POS interface: Upload/Download article master
'WP_PLU02' POS interface: material and condition (inbound and outb.)
'WTADDI01' Additionals
'WVINVE01' Store phy.inv.: phy.inv. docs outbound; count data inbound
'WVINVE02' Store phy.inv.: phy.inv. docs outbound; count data inbound
'W_WGRP01' Distribution of material groups
Regards,
Juan Carlos

POS outbound profile (Idoc type u0096 WP_PLU02)

Similar Messages

Maybe you are looking for